Subject Re: [firebird-support] Re: FB2.5SC is slow for 25-35 users
Author Thomas Steinmaurer
>> Le 26/10/2010 11:47, tomkrej a écrit :
>>> Hi, nobody had answered my question.
>>>
>>> Please would somebody help me?? Or I did a wrong question?
>>>
>>> I have new results with configuration
>>> 16kB - data page
>>> 8192 - DefaultDbCachePages
>>> 16777216 - TempCacheLimit
>>> HyperThreading in BIOS is enabled
>>> 32bit Win2003 Ent.edtion SP2
>>>
>>> Allocated memory by server process only slightly exceeds 1GB (from 4GB)
>>>
>>> The result was worsten than on friday :
>>> Problems with connection to database, disconnects during work, errors
>>> during work, PHP module had memory alocation problem during connect
>>>
>>> In Firebird.conf there are this kind of messages
>>> TS2003 Tue Oct 26 08:30:22 2010
>>> Database: D:\DATASQL\DATA\DATA.FDB
>>> Allocated 5669 page buffers of 8192 requested
>>> TS2003 Tue Oct 26 08:37:42 2010
>>> unable to allocate memory from operating system
>>> TS2003 Tue Oct 26 08:39:07 2010
>>> Operating system call CloseHandle failed. Error code 6
>>> TS2003 Tue Oct 26 08:41:00 2010
>>> Database: D:\DATASQL\DATA\DATA.FDB
>>> internal Firebird consistency check (wrong record length (183), file:
>>> vio.cpp line: 1139)
>>> TS2003 Tue Oct 26 08:44:11 2010
>>> Operating system call _beginthreadex failed. Error code 8
>>>
>>> Is anybody here who can help me??
>>> Thank You in advance, Tom
>>>
>>>
>>
>> [Non-text portions of this message have been removed]
>>
> --- In firebird-support@yahoogroups.com, Menetrier Gregory <gregory.menetrier@...> wrote:
>> Hi Tom,
>>
>> Not sure, but are you migrating from a SuperServer to a SuperClassic ?
>> If yes, i felt on the same problem.
>> You're getting out of system resources.
>> You should lower the number of PageBuffers allocated for each connection
>> (in SuperServer, the cache is shared not in SC).
>> It should be between 128 to 512 PageBuffers according to your
>> OS/Resources/Nb of client.
>>
>> Greg.
>>
>>
> Hi Tom
>
> When using SuperClassic, each connection has a separate page cache, as Greg wrote.
> Using SuperClassic is good to use multiple cores, if there are several databases on the same database server .
> If you have 35 users using the same database and mostly the same records, using superserver with a big common page cache is the better, faster solution.

From my understanding (also in my comparison sheet), SuperServer can't
utilize a SMP environment with *one* database. SS although can use
several CPUs/cores if there are more than one database involved.


--
Best Regards,
Thomas Steinmaurer
LogManager Series - Logging/Auditing Suites supporting
InterBase, Firebird, Advantage Database, MS SQL Server and
NexusDB V2
Upscene Productions
http://www.upscene.com
My blog:
http://blog.upscene.com/thomas/