On 29.11.2014 23:03, Renato Golin wrote:> On 29 November 2014 at 20:28, Dan Liew <dan at su-root.co.uk> wrote: >> Just a thought. Would it make sense to put LNT server into a Docker >> [1] container so it's portable and then we can move it over to any >> (Linux based) host we like easily and reliably? > > I think this is a great idea. We should at least try, while the other > is in "production", and if it proves stable, we switch.Proving 'stable' is not that easy. In fact LNT works flawless for me at home. I am afraid the issue only arises due to the huge database that we have after imports from several years and parallel accesses both due to LNT submits as well as users looking at LNT. Having said this, anything that allows us to have a LNT instance that can be maintained/debugged easily and where we can point our LNT testers to, will simplify debugging of this production LNT issues. Cheers, Tobias
On 30 November 2014 at 13:29, Tobias Grosser <tobias at grosser.es> wrote:> Proving 'stable' is not that easy. In fact LNT works flawless for me at > home.It's the volume, indeed.> Having said this, anything that allows us to have a LNT instance that can be > maintained/debugged easily and where we can point our LNT testers to, will > simplify debugging of this production LNT issues.Yes, maintainability and stability are more important that speed. Though, it'd be good to have database and web separate, so we can scale them differently, and as needed. Docker or cloud instances look the right way to go, for me. cheers, --renato
> Yes, maintainability and stability are more important that speed. > Though, it'd be good to have database and web separate, so we can > scale them differently, and as needed. Docker or cloud instances look > the right way to go, for me.I'm currently looking into this. It seems to be possible to have containers linked together [1] so my plan is to have a "LNT server" container (just the python stuff) and the "database" container separate and then link them together when launching the containers. Is there a way for me to obtain a copy of the current postgres database so I can test how well this works? [1] https://docs.docker.com/userguide/dockerlinks/
This was part of the motivation my cloud LNT instance. The Heroku cloud which I am running on is using a postgres cluster, not a single machine. It is well tuned for large databases.> On Nov 30, 2014, at 6:59 AM, Renato Golin <renato.golin at linaro.org> wrote: > > On 30 November 2014 at 13:29, Tobias Grosser <tobias at grosser.es> wrote: >> Proving 'stable' is not that easy. In fact LNT works flawless for me at >> home. > > It's the volume, indeed. > > >> Having said this, anything that allows us to have a LNT instance that can be >> maintained/debugged easily and where we can point our LNT testers to, will >> simplify debugging of this production LNT issues. > > Yes, maintainability and stability are more important that speed. > Though, it'd be good to have database and web separate, so we can > scale them differently, and as needed. Docker or cloud instances look > the right way to go, for me. > > cheers, > --renato > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev