On Sat, Dec 15, 2012 at 2:56 AM, Elefterios Stamatogiannakis <[email protected]> wrote: > On 15/12/2012 12:00 πμ, Maciej Fijalkowski wrote: >> >> Hi. >> >> For what is worth roughly 1/3 of the time is spent importing all the >> things. This is done in the compilation step in the ASPW, so please >> try running the select few times. Another slightly worrying thing is >> that a lot of time is spent doing utf8 decoding. Can you explain what >> in the SQL statement requires UTF8 conversion? >> >> Cheers, >> fijal >> > > Concerning running the select many times, you are right. We'll try to pay > attention to it in the future. > > This is easily achieved by copying the query in mspw_bench many times, or > increasing the "range" value so the processing load will be bigger compared > to all the other things. > > When MSPW sends something to SQLite it has to encode it to UTF-8 (default > SQLite character encoding). When it gets it back it has to convert it back > to Python's unicode. > > l.
And ASPW does the same right? I understand the general need for UTF8, I just didn't find it in this particular query. _______________________________________________ pypy-dev mailing list [email protected] http://mail.python.org/mailman/listinfo/pypy-dev
