Hi It was suggested on IRC that reporting our use of devpi here may be useful for others, so that's what I'm doing. We use devpi at my company. Actively using it is around 50 developers, 100~ python projects across 5~ branches. This amounts to 500~ releases in devpi. Many of our builds are automated and a change to a high up dependency can lead to al 100 projects being rebuilt. Each release also has documentation with it. With 2.6 we would quite often see timeouts when trying to look up packages on the devpi server. Especially when many builds were or had been occurring. We upgraded from 2.6 to 3.0.2 - I had hoped the simple index optimisation would remove these timeouts but they didn't seem to have an impact on it. We still got a lot of timeouts. I also noticed that a lot of time is spent indexing documentation. To deal with this we now run 3 --requests-only instances of devpi and 1 regular instance. We have nginx <http://doc.devpi.net/latest/quickstart-server.html> in front - I have set this up to only load balance /+status to regular and all other requests to the 3 --requests only. This has totally solved our timeout issue - the regular instance is mostly doing documentation indexing (which takes a long time when you upload 500 new releases) and the requests only instances deal with the upload/index requests admirably. Hope this might help someone and thanks for the great project. -- Andy Smith http://andrewmichaelsmith.com | @bingleybeep