Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 4 of 4 total |
multi-user performance on a network |
Sat, Mar 17 2012 8:10 AM | Permanent Link |
Ronald | Hi,
Which of these changes could speed things up? Besides Session.Max...Size and Session.Max...Count? -make tables read-0nly -change lockprotocol to lbOptimistic -use master-details relations to limit the records that are fetched -in a master-detail relation first open the master and then the client (to limit the records that are fetched) -use filters to limit the records that are fetched Thanks Ronald |
Sat, Mar 17 2012 10:08 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Ronald
>Which of these changes could speed things up? Besides Session.Max...Size and >Session.Max...Count? >-make tables read-0nly >-change lockprotocol to lbOptimistic >-use master-details relations to limit the records that are fetched >-in a master-detail relation first open the master and then the client (to >limit the records that are fetched) >-use filters to limit the records that are fetched It depends. Is your app file/server or client/server are you talking LAN or WAN? If LAN what speed? DBISAM is as smart as Tim could make it in terms of the amount of data transfered but its then down to the structure of your app and its data requirements for display and processing. As an example if your table contains a memo field it will only be transported it its displayed or acted on in some way. If you're using LAN and file/server (as I'd guess from the things you're considering) moving to client/server should give you benefits, but you'll need to alter the app to be more sql based and you need a nice powerful server. As a first stage it would be worthwhile putting a network sniffer on and seeing what the traffic is like. There may be a lot of traffic generated by other applications. Roy Lambert [Team Elevate] ps can you change your name from elevatesoft please. |
Sat, Mar 17 2012 11:32 AM | Permanent Link |
Ronald | Hi Roy,
Is is over a direct, shared-file connection on a LAN. So I have the problem of the SMB protocol. Can the suggestions help me? Ronald "Roy Lambert" schreef in bericht news:8FE8BECD-C44A-4E29-8F45-C6FFAAC41A34@news.elevatesoft.com... Ronald >Which of these changes could speed things up? Besides Session.Max...Size >and >Session.Max...Count? >-make tables read-0nly >-change lockprotocol to lbOptimistic >-use master-details relations to limit the records that are fetched >-in a master-detail relation first open the master and then the client (to >limit the records that are fetched) >-use filters to limit the records that are fetched It depends. Is your app file/server or client/server are you talking LAN or WAN? If LAN what speed? DBISAM is as smart as Tim could make it in terms of the amount of data transfered but its then down to the structure of your app and its data requirements for display and processing. As an example if your table contains a memo field it will only be transported it its displayed or acted on in some way. If you're using LAN and file/server (as I'd guess from the things you're considering) moving to client/server should give you benefits, but you'll need to alter the app to be more sql based and you need a nice powerful server. As a first stage it would be worthwhile putting a network sniffer on and seeing what the traffic is like. There may be a lot of traffic generated by other applications. Roy Lambert [Team Elevate] ps can you change your name from elevatesoft please. |
Sun, Mar 18 2012 4:59 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Ronald
>Is is over a direct, shared-file connection on a LAN. So I have the problem >of the SMB protocol. Can the suggestions help me? Unfortunately once you go multi-user you are going to get hit by a performance drop. Tweaking the buffer sizes may give you some benefit. If you increase them to far there comes a point where the management overheads outweigh the performance benefits. Tim has posted advice on this before, you'll need to search the ngs to find it though. If you can use the tables in read-only mode, and if they're not to big, you may want to consider using in-memory tables. Populate on start up from the disk based ones on the LAN. Finally make sure you have indices defined for every column you may want to use in a filter or master-detail relationship. It will cost in write performance since there's more to update but will pay off on reading. The best approach would be to convert to c/s Roy Lambert [Team Elevate] |
This web page was last updated on Tuesday, May 7, 2024 at 06:25 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |