>
> People don't have to answer all the questions - just respond to things
> that interest you or come up with your own conversation starters.
>
> On Apr 22, 5:07 pm, "Mark Nye (UIUC)" <mark...@uiuc.edu> wrote:
>> On Apr 22, 3:38 pm, "unixgirl...@gmail.com" <unixgirl...@gmail.com>
>> wrote:eads.
>>
>>
>>
>>> 1. How do you measure performance on your production system in a
>>> non-
>>> invasive way?
>>
>> We've enabled page request logging in confluence, and we graph page
>> load time as a 20 minutes moving average. We also graph slowest page
>> load and fastest page load times per 5 minutes. This is almost
>> useless
>> as an absolute performance indicator, but does show us relative
>> performance, and gives us a clue when we're encountering some issues.
>>
>> We also keep an eye out for full GC events, and a service is notified
>> if we see more than one in a 5 minutes period.
Depending on your webserver you might be able to turn request duration
logging in your access log.
I also find it useful to get an idea of the current performance by
looking at the request execution JMX stats. Confluence is instrumented
via JMX, you knew that, right?
I still would like to see more stats exposed via JXM, e.g.
http://jira.atlassian.com/browse/CONF-14912
http://jira.atlassian.com/browse/CONF-14913
>>
>>
> Are you talking about this?
> http://confluence.atlassian.com/display/DOC/How+to+audit+Confluence+-+enabling+user+access+logging
>
> On 2.8 it doesn't give page edit/create times. That is one of our
> concerns. We've considered hacking the filters but have other
> priorities.
>
> Over long, long periods of time (weeks/months) the averages can
> provide trends. Our response times minute to minute seem to vary a
> lot, so I don't know if a 20 minute moving average would hlep.
>
>
>>> 3. Do people outside your network have much slower performance, and
>>> have you done anything to improve this?
>>
>> No. To the best of my knowledge, we've never received a complaint
>> specifically related to off-campus Confluence performance.
>>
>
> Darn. A group across town has done regular testing on the same pages
> both here and across town. Typically several seconds slower. And
> inevitably whenever there is an important demo someplace our site is
> slow.
>
> The user's "slowness" experience is not always correlated to the
> access logs.
Sounds like a network problem to me. Try using ping/traceroute to
discount this possibility.
That's hard to answer. I'm the lead eng spends majority of my time on
the wikis.sun.com project. There are other engineers who pitch in from
time to time and we have a shared DBA and operations teams that are in
charge of databases, os, hw and network.
>
>
> 14. What kind of page response time do you typically see? Not just in
> the confluence access logs, but if you had a user with a stopwatch, or
> use YSlow on Firefox? What is a realistic expectation? Do you get
> users saying "You aren't as fast as Wikipedia and why aren't you on
> MediaWiki instead of Confluence?"
The initial load is terrible because confluence has close to one
million asset files which get loaded (ok, I'm kidding, but there are
way too many individual css/js files :-) ). AFAIK in Conf3.0 this was
finally fixed by concatenating and minifying these files.
Consecutive page loads are much faster because most of the asset files
are cached in the browser. Still there are some images that are not
sent with the proper caching headers and are fetched with each request
(editor, emoticons, some other icons).
After this the individual page load time depends on the number and
kind of macros used on a page, size of the page, complexity of ACL,
state of the coherence cache, https and many other factors.
Having said this, in general we see total end user page load times
somewhere between 1-7 seconds.
The page load time could be much better if the renderer was more
intelligent. Did you know that every confluence page is translated
from wiki markup and rendered almost from scratch during each page
load? There is so much opportunity for caching here, especially if
macros were required to define if their output could be cached.
/i
We patched confluence to change the ACL defaults when a space is
created.
This could be also achieved via a plugin that listens to space
creation events.
We also display a warning banner on the edit page if a page is public.
>
> 3. Do people outside your network have much slower performance, and
> have you done anything to improve this?
>
> 4. We've redesigned our main site so that the dashboard is not the
> initial page. However, we still have a lot of slowness whenever first
> logging in. Have you experienced this, and have you done anything
> about this? Our other site still uses the dashboard with 400 spaces,
> so I'd expect it to be slow...
>
> 5. How have you handled requests from groups that wanted a
> particularly specialized wiki? Or came in with a mock-up that
> resembled a website?
no customizations are allowed at our site.
>
> 6. How do you keep plugins that one group wants from impacting the
> performance of the whole site?
we are *very* conservative about plugin installation, especially when
it comes to unsupported plugins.
>
> 7. Have you hired external help for any performance improvement, or
> have you worked with Atlassian tech support, or done it on your own?
on our own
>
> 8. For sites accessible via anonymous access to the whole Internet, do
> you restrict crawling the site and/or putting it up on search sites
> like Google? And does it cause a performance hit while being indexed?
http://wikis.sun.com/robots.txt
>
> 9. Do people actually pay attention to tutorials you create?
I hope they do! :)
>
> 10. Have you found that page restrictions or space restrictions cause
> performance problems?
No, but I heard about this from people running other confluence
instances.
>
> 11. What particular plugins have you had problems with? Particularly
> third party ones.
Most of the community plugins are not suitable for instances like ours
either due to security holes or scalability issues.
>
> 12. Does your company have multiple installations of confluence, and
> what has driven you to do so?
This was proposed to us a solution to our scalability issues, but we
turned it down due to the fact that it is not solving the real issues,
adds maintenance overhead and causes user confusion.
/i