Subject | Re: [firebird-support] Performance Issues with Firebird 2.01 64 Bit - Followup information |
---|---|
Author | Steve Wiser |
Post date | 2007-08-08T15:11:59Z |
we have almost the same hardware setup as you (except we have 2.66 GHz
processors, but only 8 GB of RAM), but we have been staying away from 64
bit until I hear some positive reviews... So sorry this post doesn't
help you, but please keep on posting your results as I find them very
interesting
-steve
Dalton Calford wrote:
processors, but only 8 GB of RAM), but we have been staying away from 64
bit until I hear some positive reviews... So sorry this post doesn't
help you, but please keep on posting your results as I find them very
interesting
-steve
Dalton Calford wrote:
>
> To continue with this thread - I have been performing a series of tests.
>
> Test platform
>
> 2x Quad Core Xeon Processor 2.33Ghz
> 16 GB Ram (667 MHz.)
> 4x 73 GB 15K rpm Serial Attach SCSI - 3 Gbps Harddrives
>
> OS - Fedora Core 7 32 bit and 64 bit
>
> Test Database - a small 28GB database, with only three tables. Data
> has natural primary keys - two indexes per table
> All restore operations are coming from a single gbak file in
> transportable format.
>
> Firebird libraries set to client instead of embed.
>
> Firebird 2.01 32 bit and 64 bit, Firebird 1.53 32 bit
>
> Fedora 64 Bit, Firebird 2 64 Bit
>
> gbak -c backup.gbak /home/fb/restore1.001 -page_size 16384 -bu 10000 -v
> -y restore1.out
> Total time for the restore - 5 hours 8 minutes
> gbak -c backup.gbak localhost:/home/fb/restore2.001 -user SYSDBA
> -password masterkey -page_size 16384 -bu 10000 -v -y restore2.out
> Total time for the restore - 11 hours, 19 minutes
>
> Fedora 64 Bit, Firebird 2, 32 Bit
> gbak -c backup.gbak /home/fb/restore3.001 -page_size 16384 -bu 10000 -v
> -y restore3.out
> Total time for the restore -
>
> gbak -c backup.gbak localhost:/home/fb/restore4.001 -user SYSDBA
> -password masterkey -page_size 16384 -bu 10000 -v -y restore4.out
> Total time for the restore - 11 hours, 37 minutes
>
> Fedora 64 Bit, Firebird 1.53, 32 Bit
> gbak -c backup.gbak /home/fb/restore5.001 -page_size 16384 -bu 10000 -v
> -y restore5.out
> Total time for the restore - 3 hours 49 minutes
>
> gbak -c backup.gbak localhost:/home/fb/restore6.001 -user SYSDBA
> -password masterkey -page_size 16384 -bu 10000 -v -y restore6.out
> Total time for the restore - 4 hours, 11 minutes
>
> I am currently formating up the machine for windowsXP, and I will
> perform the exact same tests.
>
> It appears that the fb_inet_server process is much slower in generating
> indexes than gbak is.
> I monitored the process and very little CPU bouncing was going on - the
> fb_inet_server process remained on the same CPU for the whole process
> while the gbak process rarely jumped cpu's
>
> Has anyone else encountered issues like this?
>
> best regards
>
> Dalton
>
> Dalton Calford wrote:
> >
> > I am currently testing firebird 2 and I have found a number of issues
> > with speed in comparison to firebird 1.53.
> >
> > I have even found a number of issues just comparing local connections vs
> > remote connections.
> >
> > What I would like to know is if there are any known issues with Firebird
> > 2 in regards to performance?
> >
> > I have many examples of performance problems, such as a database that
> > Firebird 1.53 32bit, running on a 64 bit Linux kernel, takes 3 hours and
> > 18 minutes to restore, via localhost:/path_ to_database whereas the
> exact
> > same gbak file, takes 11 hours and 19 minutes to restore with the exact
> > same parameters on Firebird 2.01 64 bit.
> >
> > Running a variety of queries via isql shows that the 32 bit 1.53 version
> > is much faster than the 2.01 64 bit version.
> > Is this a problem with 64 bit Firebird? Are there any significant
> > changes that I must deal with in order to get the performance with 2.01?
> >
> > Thanks in advance
> >
> > Dalton
> >
>
>