Jeroen T. Vermeulen wrote:
> Those three URLs for reproducible timeouts work for me now, and are in
> fact quite fast. It's possible that their data has been moved into
> caches since the rollout.
>
> Meanwhile we've identified another suspect that has more to do with
> system configuration than with programming. I'm not sure when this is
> going to be addressed but we are making it a priority and it shouldn't
> take long.
>
Not cache - I was able to create a targeted index for the failing query.
This should last until we can address the config issue.
Jeroen T. Vermeulen wrote:
> Those three URLs for reproducible timeouts work for me now, and are in
> fact quite fast. It's possible that their data has been moved into
> caches since the rollout.
>
> Meanwhile we've identified another suspect that has more to do with
> system configuration than with programming. I'm not sure when this is
> going to be addressed but we are making it a priority and it shouldn't
> take long.
>
Not cache - I was able to create a targeted index for the failing query.
This should last until we can address the config issue.
-- www.canonical. com/ www.ubuntu. com/
Stuart Bishop <email address hidden> http://
Canonical Ltd. http://