[dev] performance problem -> does horde use raw sockets

[Sebastian Birnbach]

Mike,

your input is much appreciated.

Another PHP-intensive application (PHPmyAdmin) is running fine so it's not
a real performance problem but clearly related to Horde. It seems to me the
trouble began when I upgraded from PHP 5.4 to 5.5 but I am not sure. Sure
is only that it used to be a lot faster and that a reinstallation from
scratch (both operating system and applications) did not fix it. It is
probably some wierd thing with the jail it is running in, a permissions
problem or a network connection that doesn't work out. There is little left
to test, the sockets from user space is one thing. If that fails... maybe
investing in new hardware that runs without jails is less expensive than
drilling to the bottom of this :-((

Kind regards and more updates as soon as I get to it

  Sebastian

2015-06-12 16:07 GMT+02:00 Michael J Rubinsky <mrubinsk at horde.org>:

>
> Quoting Sebastian Birnbach <birnbacs at gmail.com>:
>
>  All,
>>
>> I have made the host's ethernet interface available inside the jail and
>> checked with tcpdump if PHP secretly downloads a file as a reason for the
>> 5-seconds-delay to every HTTP request. This does not seem the case,
>> nothing
>> suspicious is going on.
>>
>> Is it possible that horde is using raw sockets for something? A ping to
>> some internet host maybe? This concerns the base system, not one of the
>> applications (nag, kronolith etc), there are none installed yet.
>>
>
> No, the base Horde app shouldn't be pinging anything under normal use
> (assuming no external APIs such as Weather or Twitter etc...) were
> configured for use in the Portal page . The only place I can think of that
> would do any kind of request is the configuration page, which might be
> polling pear.horde.org for updated packages if requested to do so.
>
> Shot in the dark, as I haven't been reading this thread fully, but maybe
> it's related to compressing javascript and not being able to save the
> compressed file (so it must spend time compressing on each request)? Try
> temporarily turning off javascript and/or css caching maybe?
>
> Another thought - have you tried just requesting a basic test script on
> the server to be sure it's not some issue/latency with PHP itself?
>
> --
> mike
> The Horde Project
> http://www.horde.org
> https://www.facebook.com/hordeproject
> https://www.twitter.com/hordeproject
>
> --
> dev mailing list
> Frequently Asked Questions: http://wiki.horde.org/FAQ
> To unsubscribe, mail: dev-unsubscribe at lists.horde.org
>