Mailinglist Archive: opensuse (908 mails)

< Previous Next >
Re: [opensuse] apache 2.4 performance issue / processwire.
  • From: Per Jessen <per@xxxxxxxxxxxx>
  • Date: Fri, 10 Jun 2016 22:08:36 +0200
  • Message-id: <njf6o4$lhj$>
Dave Howorth wrote:

On Fri, 2016-06-10 at 17:42 +0200, Per Jessen wrote:
Dave Howorth wrote:
I take it reorganizing the paths or using a ramfs cache are not
sensible for whatever reason?

It's shared environment, minor changes that don't change the general
scheme would be fine, I could even disable open_basedir.

I haven't thought about the implications of disabling open_basedir at

It seems to be the main stumbling block - I haven't had time to think it
through yet.

Could you try connecting an iSCSI filesystem to your test machine?
That might prove whether iSCSI is an essential feature of the problem.

Not a bad idea, that should be asy enough to do.

If it is then adding a local hard disk to the server might be the
cheapest solution? Though probably cause you maintenance issues in the

Yeah. It would mean a minimum of two disks, and then it's not too far to
a dedicated server.

Have you got anywhere with enquiries to processwire or PHP?

Well -

a) processwire, never even got my forum registratrion confirmation.
b) I tried logging into to update the bug, but my
old userid doesn't seem valid anymore - login only possible with addresses. :-)

The bug seems moribund, in that only people who have the problem have
posted to it recently, not people who might play a part in its
solution. So I thought it might be more productive to post to the
mailing list. But if you already had a login, I can see why the bug
would be first port of call.

I'll check the mailing list too, but I went to, got
redirect to where it's really clear how to
subscribe to a list. I think it's probably subscribe by email only.

Per Jessen, Zürich (18.8°C) - free dynamic DNS, made in Switzerland.

To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups