tag:blogger.com,1999:blog-5091343484575635160.post3571796122810059484..comments2019-11-14T06:01:13.589+00:00Comments on Estuary IT: What A Difference A Drive MakesUnknownnoreply@blogger.comBlogger1125tag:blogger.com,1999:blog-5091343484575635160.post-48789232887132615912014-07-01T10:50:03.074+01:002014-07-01T10:50:03.074+01:00Wanted to share some findings for those that have ...Wanted to share some findings for those that have considered whether upgrading to a SSD drive might be a good thing for SAGE users. <br /><br />We installed a SSD Drive into our server, and we've isolated it as a separate drive so it contains ONLY the Sage Data. We share this folder as per normal. Sage backups are saved onto a regular drive folder, not on the SSD. <br /><br />We had two identical work stations side by side, on a network. One logged into the original data path on a standard hard drive, the other was logged into the company on the SSD drive. Both companies were restored test data from one of our backups - both identical information. <br /><br />We timed the responses of updating the ledgers of 10 invoices. We ran 3 tests and the best performance difference was where the SSD Drive took 12 seconds to update, where the regular drive took 33 seconds on the same files. This is still over a network - not local data. <br /><br />We then did a maintenance check on the networked machines. The Company on the SSD took 2 mins 17 seconds to run the maintenance check where the company on a regular drive took 3 mins 6 seconds. Again, this was checked over the network. <br /><br />As a background to our company, we have 5 companies accessing their relevant data on the regular drives at the moment, I can only imagine the amount of dancing around the drive head is doing to keep up with the demand. However, considering the fact that the SSD has almost 0 ms seek time, I am seriously considering moving all the data onto the SSD drive and running from there. MChttps://www.blogger.com/profile/16244095066826315253noreply@blogger.com