You might be fooled by the caches. Depending on what other visitors visit
and the mysql query cache, the time to redraw the page might take more or
less.
I suggest you look at the mysql queries and you run them manually with the
"NO CACHE" setting to see if the volume of data creates the slowness issue.
I think I found the issue. With the new indexes there are no indexes on the
ASE_REQUESTID column
Try running this query
select /*! SQL_NO_CACHE */ activityev0_.ase_eventid as ase1_32_,
activityev0_.ase_requestid as ase2_32_, activityev0_.ase_stream as
ase3_32_, activityev0_.ase_date as ase4_32_, activityev0_.ase_priority as
ase5_32_, activityev0_.ase_type as ase6_32_, activityev0_.ase_application
as ase7_32_, activityev0_.ase_user as ase8_32_, activityev0_.ase_wiki as
ase9_32_, activityev0_.ase_space as ase10_32_, activityev0_.ase_page as
ase11_32_, activityev0_.ase_url as ase12_32_, activityev0_.ase_title as
ase13_32_, activityev0_.ase_body as ase14_32_, activityev0_.ase_version as
ase15_32_, activityev0_.ase_param1 as ase16_32_, activityev0_.ase_param2 as
ase17_32_, activityev0_.ase_param3 as ase18_32_, activityev0_.ase_param4 as
ase19_32_, activityev0_.ase_param5 as ase20_32_ from activitystream_events
activityev0_ where
activityev0_.ase_requestid='**55616298-1320309892000-**18xovYho'
order by activityev0_.ase_date desc
If it takes even more than 0.5 second given the repetitivity of this type
of query this can lead to 10 seconds in the end.
You can see your indexes like that:
show indexes from activitystream_events;
Then create this index:
create index ase_requestid on activitystream_events (ase_requestid(200));
and rerun the query and the activity stream.
I believe you might be better of having CheckIndexes create additional
indexes for you even if that leads to duplicated indexes, since there might
be some more missing indexes. I've sent a mail to devs to discuss why the
indexes in Admin Tools are different than the ones now automatically
created by XWiki.
Ludovic
2011/11/5 Yang Li <yang.lee.cool(a)gmail.com>
Oh, it is so weird, after logout and login, the
?xpage=contentview load
time increased from 4 to 10....
and almost another 2 seconds with the skin...
于 2011/11/5 15:24, Ludovic Dubost 写道:
So that means there would be additional time
consumed by something else
than the activity stream.
Do you have anything special in the skin ? What does the speed look like
with ?skin=colibri in the URL
Ludovic
2011/11/5 Yang Li<yang.lee.cool(a)gmail.com>
于 2011/11/5 15:08, Ludovic Dubost 写道:
This won't do much. How fast is the activity page with
?xpage=contentview
in the URL. This is the core activity stream
time
Yes, I found that, no sensable improvement of the performance in an
intranet.
My profile page with ?xpage=contentview is loaded about 4 seconds. Much
better than 10 or 20....
______________________________****_________________
users mailing list
users(a)xwiki.org
http://lists.xwiki.org/****mailman/listinfo/users<http://lists.xwiki.org…
<http://**lists.xwiki.org/mailman/**listinfo/users<http://lists.xwiki.org/mailman/listinfo/users>
______________________________**_________________
users mailing list
users(a)xwiki.org
http://lists.xwiki.org/**mailman/listinfo/users<http://lists.xwiki.org/m…
--
Ludovic Dubost
Founder and CEO
Blog:
http://blog.ludovic.org/
XWiki:
http://www.xwiki.com
Skype: ldubost GTalk: ldubost