Our binaries and all the necessary files to run Sampa keep growing. Right now, Sampa is a 20MB deployment. To transfer this data from our 768Kbps-uplink to the datacenter can take anywhere from 5 to 20 minutes.
Our deployment script would copy the content and deploy it as it was being copied. The problem with that strategy is that IIS doesn't have all the files ready to switch-over to the new version, so, between the first and last file notification it would take 2-3 minutes, thus, upgrading the Sampa site service would take the system "offline" for about 2-3 minutes. Well, the queue will not stay with a request for more than 90 seconds or so, so a lot of page requests were being dropped.
By doing a tiny change to the deployment script, we went from 2-3 minutes of downtime to 40 seconds!
All that we had to do was to copy the files to a temporary folder and from the temporary folder copy to the target folder. Works like a charm
I always wondered was most applications, during setup, don't copy the content from the CD to the disk and then install if from the disk. That would be so much faster instead of doing disk-seeks on a slow CD-ROM.
Subscribe to this Site
Comments for "400% perf improvement on dep...
October, 2007
