|Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM Client/Server » View Thread|
|Messages 1 to 3 of 3 total|
|Massive performance hit after upgrade to 4.45 and 64 bit server|
|Sat, Oct 27 2018 8:43 AM||Permanent Link|
I have a legacy application which I converted to client / server over the last year. It was working pretty well but I then upgraded DBISAM and made some architecture changes and performance has gone through the floor.
I upgraded DBISAM on both client and server from approximately 4.43 to 4.45
The client application is compiled using Delphi 7
The server is basically the vanilla DBISAM server with minor changes around loading config / handles passwords - but I ported this to the latest 64 bit version that ships 4.45 - compiled with XE5
So I have a win32 client using DBISAM 64 bit server and truly terrible performance on large datasets.
Note I know there are may performance opportunities that I have not fully exploited in the move to client / server - I will cover these in other questions. My primary issue however is to pin down why performance has dropped so dramatically with this upgrade.
Any suggestions please - including comments on diagnostic steps.
|Tue, Oct 30 2018 1:05 PM||Permanent Link|
Tim Young [Elevate Software]
Elevate Software, Inc.
<< So I have a win32 client using DBISAM 64 bit server and truly terrible performance on large datasets. >>
This is a little too broad to result in any sort of meaningful answer. If you could post more information on the application architecture, etc., it would help. For example, is your application primarily using navigational access, or SQL access ? Are you using lookup fields ?
Here are some places to start:
|Wed, Oct 31 2018 6:52 AM||Permanent Link|
Firstly - I apologise for the certainty in my post that the performance hit was as a result of the DBISAM upgrade. I was relying on memory - but when I checked git there were other changes such as the memory manager - also the customers might have made changes to their network which might account for the seriousness of the problems.
I have been digging into the detail using a profiler and am treating this as a broader piece of work - it is looking like a few DBISAM queries are causing me problems but other things account for most of the latency.. so I will fix those first and come back here with questions if still stuck.