Puschus Barrett
asked this on November 01, 2011 06:33
What is the realistic max number of computers PDQ Inventory will support? Are there any plans for an SQL Express backend for better performance and more possible client computers?
I find that after around 700 computers, the console is quite sluggish - is this expected with this many machines or more?
Comments
Yes, we do have plans to allow other relational databases to be used.
In the meantime, the limitation isn't with the database (SQLite) as much as it is with the Console machine specs. How much memory do you have on the console machine?
I have 8gb of RAM, win 7 64b
The current version of the software has had most of the performance tuning geared to around 500 computers. We're currently working on performance improvements for larger numbers. Most of the performance issues seem to revolve around getting changes in the database from the scanning service and loading them into the interface, there are a lot of thing we can do here to make it faster.
Where, in particular, do you notice most of the sliggishness? Is it just a general slowdown or do you notice it more in certain places or during certain operations?
Mostly when switching between collections or double-clicking on a computer to bring up the inventory. Certainly not a show-stopper, but because it was during data-access operations I assumed it was the sqlLite backend causing the latency.
You're right that it's the data access code that's the bottleneck, as you would expect in such a heavily database oriented application. SQLite may be responsible for some of it, it's performance profile is quite a bit different that SQL Server, in that some operations are faster and others are slower. We're still very early on in the development cycle, so you can look forward to some performance gains in the future.