Обсуждение: planning for perf farm app
Hi everyone, I've been making some progress on some perf farm stuff and I just wanted to make sure I understand how to best work with the pg infrastructure when (if) we get far along to deploy something. We're planning on having a django application for distributed clients to be able to upload results, and for users to review results. Plus a supporting postgres database. Similar to how the build farm is structured. So I'm wondering things like, should we stick to a particular django or python version, proof things on a particular linux distro (debian stretch?) and what not. And anything else we should be mindful of. Thanks! Regards, Mark -- Mark Wong http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, RemoteDBA, Training & Services
On 02/13/2018 10:58 PM, Mark Wong wrote: > Hi everyone, Hi Mark! > > I've been making some progress on some perf farm stuff and I just wanted > to make sure I understand how to best work with the pg infrastructure > when (if) we get far along to deploy something. good to hear that progress is made on that front! > > We're planning on having a django application for distributed clients to > be able to upload results, and for users to review results. Plus a > supporting postgres database. Similar to how the build farm is > structured. ok > > So I'm wondering things like, should we stick to a particular django or > python version, proof things on a particular linux distro (debian > stretch?) and what not. And anything else we should be mindful of. > Thanks! Well the postgresql.org infrastructure is running debian stretch and all our current django applications are on django 1.8.18 in a custom (but internally packaged) virtualenv - we have not yet decided on what version we will move to next (because 1.8 will be EoS'd in April) but it will likely be an LTS version. In general we very heavily rely on packaged software for maintainability so I would advise to stay away from versions of software that are not packaged in stretch (or debian in general) - for postgresql itself we use apt.postgresql.org so any version that is available there should be fine. Also note that you application should be designed to not require any root-user interaction because we usually do not hand out that kind of privilege. Stefan
Hi Stefan, On Thu, Feb 15, 2018 at 01:06:39PM +0100, Stefan Kaltenbrunner wrote: > On 02/13/2018 10:58 PM, Mark Wong wrote: > > Hi everyone, > > Hi Mark! > > > > > I've been making some progress on some perf farm stuff and I just wanted > > to make sure I understand how to best work with the pg infrastructure > > when (if) we get far along to deploy something. > > good to hear that progress is made on that front! > > > > > We're planning on having a django application for distributed clients to > > be able to upload results, and for users to review results. Plus a > > supporting postgres database. Similar to how the build farm is > > structured. > > ok > > > > > So I'm wondering things like, should we stick to a particular django or > > python version, proof things on a particular linux distro (debian > > stretch?) and what not. And anything else we should be mindful of. > > Thanks! > > Well the postgresql.org infrastructure is running debian stretch and all > our current django applications are on django 1.8.18 in a custom (but > internally packaged) virtualenv - we have not yet decided on what > version we will move to next (because 1.8 will be EoS'd in April) but it > will likely be an LTS version. > > In general we very heavily rely on packaged software for maintainability > so I would advise to stay away from versions of software that are not > packaged in stretch (or debian in general) - for postgresql itself we > use apt.postgresql.org so any version that is available there should be > fine. > > Also note that you application should be designed to not require any > root-user interaction because we usually do not hand out that kind of > privilege. Ok, all sounds good. I'll try to follow suit. Thanks! Regards, Mark -- Mark Wong http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, RemoteDBA, Training & Services
On Thu, Feb 15, 2018 at 1:06 PM, Stefan Kaltenbrunner <stefan@kaltenbrunner.cc> wrote:
On 02/13/2018 10:58 PM, Mark Wong wrote:
> Hi everyone,
Hi Mark!
>
> I've been making some progress on some perf farm stuff and I just wanted
> to make sure I understand how to best work with the pg infrastructure
> when (if) we get far along to deploy something.
good to hear that progress is made on that front!
>
> We're planning on having a django application for distributed clients to
> be able to upload results, and for users to review results. Plus a
> supporting postgres database. Similar to how the build farm is
> structured.
ok
>
> So I'm wondering things like, should we stick to a particular django or
> python version, proof things on a particular linux distro (debian
> stretch?) and what not. And anything else we should be mindful of.
> Thanks!
Well the postgresql.org infrastructure is running debian stretch and all
our current django applications are on django 1.8.18 in a custom (but
internally packaged) virtualenv - we have not yet decided on what
version we will move to next (because 1.8 will be EoS'd in April) but it
will likely be an LTS version.
Just to keep you updated, we do now have fully supported 1.11 out in production for a number of our sites, so that's the current target.
Currently we only do 1.11 on python2, we do not have a python3 environment set up for it yet. 1.11 on py3 will be the next step following this one, but we aren't quite there yet.
On Fri, Mar 09, 2018 at 10:52:26PM +0100, Magnus Hagander wrote: > On Thu, Feb 15, 2018 at 1:06 PM, Stefan Kaltenbrunner < > stefan@kaltenbrunner.cc> wrote: > > > On 02/13/2018 10:58 PM, Mark Wong wrote: > > > Hi everyone, > > > > Hi Mark! > > > > > > > > I've been making some progress on some perf farm stuff and I just wanted > > > to make sure I understand how to best work with the pg infrastructure > > > when (if) we get far along to deploy something. > > > > good to hear that progress is made on that front! > > > > > > > > We're planning on having a django application for distributed clients to > > > be able to upload results, and for users to review results. Plus a > > > supporting postgres database. Similar to how the build farm is > > > structured. > > > > ok > > > > > > > > So I'm wondering things like, should we stick to a particular django or > > > python version, proof things on a particular linux distro (debian > > > stretch?) and what not. And anything else we should be mindful of. > > > Thanks! > > > > Well the postgresql.org infrastructure is running debian stretch and all > > our current django applications are on django 1.8.18 in a custom (but > > internally packaged) virtualenv - we have not yet decided on what > > version we will move to next (because 1.8 will be EoS'd in April) but it > > will likely be an LTS version. > > > > Just to keep you updated, we do now have fully supported 1.11 out in > production for a number of our sites, so that's the current target. > > Currently we only do 1.11 on python2, we do not have a python3 environment > set up for it yet. 1.11 on py3 will be the next step following this one, > but we aren't quite there yet. Ok. If accepted, I'll be sure to instruct the student to use a python2 environment. Regards, Mark -- Mark Wong http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, RemoteDBA, Training & Services