List:MySQL++« Previous MessageNext Message »
From:Chris Frey Date:October 26 2005 6:11pm
Subject:Re: Retrieving 300K+ records
View as plain text  
On Wed, Oct 26, 2005 at 10:46:49AM -0700, Earl Miles wrote:
> >Before you jump completely to C, you might try using the .at() function
> >to reference fields by index instead of by name.  This removes the repeated
> >name lookup on each cycle of your loop.
> >
> 
> The name lookups aren't what cause the slowdown (for me, at least) -- it's 
> translating from a mysql row to a MySQL++ Row object that takes all the 
> time.

Interesting.  Looking at the code, there are about 3 objects, one of which
contain a vector of strings, involved in moving the data.

I think this goes back to that iterator optimization that I never got
around to. :-)  There might have even been a patch floating around if
memory serves.

- Chris

Thread
SSQLS contained within class definition compilation issueswilliam.lieberman25 Oct
  • Retrieving 300K+ recordsAlex Vishnev25 Oct
    • Re: Retrieving 300K+ recordsEarl Miles25 Oct
      • RE: Retrieving 300K+ recordsAlex Vishnev25 Oct
        • Re: Retrieving 300K+ recordsWarren Young27 Oct
      • RE: Retrieving 300K+ recordsAlex Vishnev26 Oct
        • Re: Retrieving 300K+ recordsWarren Young27 Oct
          • RE: Retrieving 300K+ recordsAlex Vishnev27 Oct
    • Re: Retrieving 300K+ recordsChris Frey26 Oct
      • Re: Retrieving 300K+ recordsEarl Miles26 Oct
        • Re: Retrieving 300K+ recordsChris Frey26 Oct
          • RE: Retrieving 300K+ recordsAlex Vishnev26 Oct
            • Re: Retrieving 300K+ recordsEarl Miles26 Oct
            • Re: Retrieving 300K+ recordsChris Frey26 Oct
  • Re: SSQLS contained within class definition compilation issuesahnkle28 Oct
    • New FeaturesFabricio Mota29 Oct
RE: SSQLS contained within class definition compilation issueswilliam.lieberman25 Oct
  • Re: SSQLS contained within class definition compilation issuesWarren Young27 Oct
Re: SSQLS contained within class definition compilation issuesWarren Young27 Oct