Deployment of Latest Build Takes Minutes not Seconds
The solution isn't large or small, maybe about 50MB in total (I'd have to check) but I'm finding that deployments are taking longer than advertised. Admittedly, I should get some of the static content on to a proper CDN so I don't have to go through a git push to master for non-code changes but are there any other tips for deploying in '15 seconds'?
Discussions are closed to public comments.
If you need help with AppHarbor please
start a new discussion.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by rune on 28 Jan, 2011 02:36 AM
Hi,
there could be a few reasons why building and deploying a website takes longer than 15 seconds to deploy. First of all, if you have a large solution that takes a lot of time to build it may take some time until it gets there. We're looking into using some larger instances for our build servers to reduce the amount of time, but apart from that there's not much we can do - building is a process we can't accelerate in a lot of ways.
If you have stuff in your solution that isn't required by your website to run you could always make an AppHarbor.sln file that contains only the required projects. This would reduce the build time as less would have to be build.
Finally, if you have a lot of long-running tests that takes a lot of time to run you could always optimize those. Testing is done as part of the build process and optimizing them would reduce that process.
As for actually deploying the application after a build, it shouldn't take minutes if your project is of the size your mention. You may have stumbled into a queue on a web server so it wasn't processed as fast a couple of times. If this is a repeated pattern though, we would like to look into it with you. You can determine how long it takes to deploy the application (without building it) by clicking the "deploy" link next to a build that has been previously deployed. If that process takes more than 15-30 seconds we would really like to know about it. We want this part to be particularly fast, as this is also the way people can roll back a bad deployment using our interface, so it's a critical part of the system.
That being said we also have to actually move the files physically in order to deploy it on a web server so naturally it will take longer for large projects. As you propose, using a CDN for any static content, rather than including it in the repository, can definitely reduce the amount of time used on moving your application to our web servers.
We're always looking to improve these processes and as you use the platform I'm sure you will continuously experience better performance as we get more and more parts optimized.
Let me know if I should take a look at your application and see if we can optimize it in some way.
Best regards,
Rune
tt closed this discussion on 19 Feb, 2011 10:26 PM.