Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 3 of 3 total |
Multi-user performance solution? |
Thu, Feb 15 2007 2:30 PM | Permanent Link |
Michael Fullerton | Suppose I have a multi-user shared-data app with potentially huge
tables (20+MB). With this app the larger tables contains important data which requires them to be refreshed frequently. This causes performance problems. I was thinking of reducing this by using an ini file in the data path to record when a table has been modified. When the table needs to be refreshed, check the shared ini file to see if the table has been modified since the last check. Only refresh if it has been modified. Good idea or no? Of course it would even be better if you could somehow correlate the changed records with the subset that relates to the current situation in the app. For example in a billing app, refresh only if any records related to the invoices being viewed have changed. ___ Free Project Time Tracker for Delphi Developers http://www.cybermatrix.com/pcdelphi.html |
Thu, Feb 15 2007 2:54 PM | Permanent Link |
"Jose Eduardo Helminsky" | Michael
I would use another table to do that instead of INI file (easier than) because you will have to deal with file locks, wait for locking, and etc, things that a simple table already does internally. Eduardo "Michael Fullerton" <fullerm@spamkiller-remove-cybermatrix.com> escreveu na mensagem news:unc9t21cnk9v587a1vhl2v1fd5fioht51e@4ax.com... > Suppose I have a multi-user shared-data app with potentially huge > tables (20+MB). With this app the larger tables contains important > data which requires them to be refreshed frequently. This causes > performance problems. I was thinking of reducing this by using an ini > file in the data path to record when a table has been modified. When > the table needs to be refreshed, check the shared ini file to see if > the table has been modified since the last check. Only refresh if it > has been modified. Good idea or no? > > Of course it would even be better if you could somehow correlate the > changed records with the subset that relates to the current situation > in the app. For example in a billing app, refresh only if any records > related to the invoices being viewed have changed. > > ___ > Free Project Time Tracker for Delphi Developers > http://www.cybermatrix.com/pcdelphi.html |
Fri, Feb 16 2007 3:07 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Michael,
<< Suppose I have a multi-user shared-data app with potentially huge tables (20+MB). With this app the larger tables contains important data which requires them to be refreshed frequently. This causes performance problems. >> A refresh in DBISAM only involves checking the table header to see if anything has changed, so it doesn't actually refresh anything unless something has changed in the table. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Wednesday, April 24, 2024 at 11:07 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |