>> I realize that this is probably a Windows or Apache issue rather than
>> a MoinMoin one.
>
> Why?
Because it is the Apache process that consumes the resources, not
Python, and because the error log grows 100 MB a day.
> As the Moin sources in MoinMoin.util.filesys say, this is needed for stat,
> rmdir and mkdir on win32, but I couldn't find any explanation of it or any
> experiences others have had.
I added that (slightly silly) wrapper code long ago because it simply
did not work without on windows.
I never
On 12/16/2013 10:10 AM, Kai Jaeger wrote:
> I realize that this is probably a Windows or Apache issue rather than
> a MoinMoin one.
Why?
> Anyway: because I had to through Apache's error as well as the access
> log I found something strange totally unrelated to my problem:
>
> The most popular p
I realize that this is probably a Windows or Apache issue rather than
a MoinMoin one.
Anyway: because I had to through Apache's error as well as the access
log I found something strange totally unrelated to my problem:
The most popular page on my wiki is:
... - - [16/Dec/2013:09:04:01 +] "GE
On Saturday 14. December 2013 08.46.31 you wrote:
> Thanks Paul, but there is no Virus checker running on the machine.
Sorry, but I had to mention it: something for the checklist, as I said. The
other thing I thought about was that a remote filesystem might be involved.
Could that be the case?
Thanks Paul, but there is no Virus checker running on the machine.
On Fri, Dec 13, 2013 at 1:21 PM, Paul Boddie wrote:
> On Friday 13. December 2013 13.39.14 Thomas Waldmann wrote:
> >
> > > Looking into the ACCESS log nothing obvious caught my eye. The ERROR
> log
> > > is much more interestin
On Friday 13. December 2013 13.39.14 Thomas Waldmann wrote:
>
> > Looking into the ACCESS log nothing obvious caught my eye. The ERROR log
> > is much more interesting. There are thousands of entries like this:
> >
> > WARNING MoinMoin.util.filesys:110
> > mkdir(('...datacacheaplwiki\
> I am suffering from performance problems. Delivery of pages can take up
> to 80 seconds. See http://aplwiki.com/
>
> The CPU is kept busy by the http process.
You could enable the timing log feature (see docs/CHANGES in the repo)
to see what requests are really taking long.
I recently also ad
Moin!
I am suffering from performance problems. Delivery of pages can take up to
80 seconds. See http://aplwiki.com/
The CPU is kept busy by the http process.
Looking into the ACCESS log nothing obvious caught my eye. The ERROR log is
much more interesting. There are thousands of entries like th
