How Octopus 3.0 blows 2.6 out of the water
Blog post from Octopus Deploy
Octopus Deploy's update to version 3.0 focused on significantly enhancing performance, particularly for large and complex deployment scenarios. This was achieved by rewriting the persistence layer to use SQL Server instead of Raven, replacing the communication layer Pipefish with Halibut, and making substantial improvements to logging and orchestration. During testing, a complex deployment involving numerous NuGet feeds, steps, child package steps, and variable sets completed in 2 hours and 41 minutes on version 3.0, compared to 4 hours and 18 minutes on version 2.6, demonstrating a marked reduction in CPU and memory usage. The update promises not only better performance but also the upcoming introduction of exciting new features.