From: Jeff Garland (jeff_at_[hidden])
Date: 2007-03-17 13:10:39
Yuriy Koblents-Mishke wrote:
> On 3/15/07, Jeff Garland <jeff_at_[hidden]> wrote:
>> Raw, unadulterated speed.
> I measured a timing of my recent Python & MySQL & file I/O
> application. It involved a lot of sequential file I/O
> read/verify/reformat/output, a lot of regexp parsing of the data, and
> not really much DB access (gulped several dictionaries from MySQL
> during startup, the biggest one with 0.5 millions rows). With
> substantial amount of data to process the program was somewhat slow. I
> thought that it spends most of time in regexp parsing and looked if it
> would make sense to rewrite the codes in C++.
> Turned to be that it ate roughly 15 seconds of CPU time during 15
> minutes runs. Personally, I dropped the idea to rewrite it in C++ for
> its "raw, unadulterated speed" after the measurements...
That's fine...I don't want to start a performance argument here. And, I agree,
that for many, many apps there's no advantage. That doesn't preclude the fact
that for some there is.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk