Comment 10 for bug 618019
Revision history for this message
| Gustavo Niemeyer (niemeyer) wrote Re: OOPS may be underrepresenting storm/sql time | #10 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
As we discussed online:
- You're right, it's 1/10th the time for fetchmany() (arraysize will be set to 10 items at a time by default)
- We'll need two trace calls for every fetch, or rowcount/10*2 on fetchmany.
- I'm still a bit unhappy that we're adding O(n) overhead on the retrieval of results to debug an issue which isn't entirely related to the application logic (timeouts will mean network problems, or problems in the database machine).
- I realize it's important to you. Let's move ahead and get an implementation in a straightforward way and discuss from there.