3. 3
Co-founder of ACC Poland Ltd., the first Polish
●
Plone company (past)
Plone consultant at RedTurtle Technology -
●
based in Ferrara (present)
Plone-based and Lotus-based web applications
●
15. 15
Far, far away
Response time, secs. Longest transaction, secs.
18 60
16
50
14
12 40
10
50 CU 50 CU
30 200 CU
200 CU
300 CU
300 CU
8
6 20
4
10
2
0 0
Django RubyOnRails TurboGears Plone Django RubyOnRails TurboGears Plone
16. 16
But comparing with Zope2
Response time, secs.
18
16
14
12
10
50 CU
200 CU
8
300 CU
6
4
2
0
Django + Psyco RubyOnRails 1.2.1 TurboGears Plone Zope2
17. 17
What can we do...
Do not treat Plone as a framework
●
For some use cases:
●
use ContentMirror + fast framework (django,
pylons, repoze)
But what about enterprise intranet solutions?
●
18. 18
Plone for enterprise intranet
Large number of users (more than 500) and
●
documents (more than 100 000)
A lot of simultaneous write requests (>20 CU/s)
●
Using of caching limited
●
Slowest acceptable resp. time <10 seconds
●
the limit for keeping the user's attention focused
[Miller 1968; Card et al. 1991]
47. 47
ZEO scalability problem
Response time, secs. 20 CU
45
40
35
30
25
1:10
4:20
20
6:18
10:30
15
10
5
0
Log in Folder view Create document Save document View Publish Home page Logout
48. 48
ZEO scalability problem
% Errors (ConflictErrors), 20 CU
60
50
40
1:10
30
4:20
6:18
10:30
20
10
0
Log in Folder view Create document Save document View Publish Home page Logout
49. 49
Plone intranet limits
ZODB is slow when handling concurrent writes
●
transactions
Scalability problem using flat ZEO
●
Missing 'out of the box' performance
●
(comparing to other framworks, CMS)