Subject | RE: [ib-support] IB Server is SLOW!!!!!!!!!!!! |
---|---|
Author | Leyne, Sean |
Post date | 2002-03-07T13:15:59Z |
Dan'l
above that setting actaully reduces performance.
in many cases.
that if the server is restarted that the affinity setting is restored
correctly.
application, TTables!!!! and most likely poorly indexed/optimized
queries.
Sean
> ... I have set the number of page buffers to 65535 ...Change this value to 10,000 -- there has been some evidence that a value
above that setting actaully reduces performance.
> ... set the processing priority to 2...Restore that value to the original, this value has the opposite effect
in many cases.
> ... ib_affinity to set the cpu to 1...I would suggest you use the IBCOnfig CPU_AFFINITY setting, it ensure
that if the server is restarted that the affinity setting is restored
correctly.
> ...I use the NT perfomance counters to watch IBServer. It isYour performance problem can best be traced to a poorly designed
> frequently maxed out at the top (flatlined!)
>
> I have included an external DCOM app to monitor what the main app
> is doing (reports, grids, forms). When several resource hungry
> reports are requested at the same time, I can see that the engine is
> maxed out.
>
> The app is using TTables (not my idea, someone else wrote the
> app). I have tried to make sure that all tables and queries are
> closed when the app starts and when the forms (~600 of them) are
> created.
application, TTables!!!! and most likely poorly indexed/optimized
queries.
Sean