Enhancement
Scalability tests
Issue description
See how Topincs scales in these two directions: number of topics and statements, number of concurrent users.
Developer comments
The current Topincs 5.2 cannot handle masses of data. 1000 topics max. With Topincs 5.3 that will be different. It will be able to handle significantly more data. Goal is 100.000 topics. Realistic should be 50.000.
Concurrency: i did not perform any elaborate test, but here is my guess: Topincs will perform well on large data sets, _if writing is rare_. The reason for this is that every write empties the response cache. With a more elaborate cache expire algorithm this can be improved, in particular it would be useful to know the change date of a page. But most importantly all access to large lists of topics should be kept to a minimum. This can be achieved by smart assembling of likely options. Eventually a load on scroll mechanism could be implemented on the start page.
Topincs 5.3 was tested with 20.000 topics on a 5 year old macbookpro and showed good performance. In Topincs 5.2 the start page was the bottleneck in this aspect since it contained all domain topics. Now only the domain types and their instance counts are displayed. If a type has 10.000 instances it will naturally take some time to query them, sort them, convert them into links, transfer them and insert them into the page. It might be smart to avoid that.
|
Work sessions2
Start |
2011-01-12T11:20:17
|
End |
2011-01-12T16:44:00
|
Participant |
Robert Cerny
|
Summary |
* Creation a larger topic maps (2000 topics, 5000 topics, 10000 topics)
* Benchmarking start page and table page unbearable with even 2000 topics
* Creation of database indexes helps
* Start page ok up to 2000 topics, range acceptable (5sec) with 2000 topics, 5000 topics takes longer
* Table page ok, takes about 10 sec to load with 5000 entries, sorting takes 8 seconds
|
Start |
2011-01-13T14:23:31
|
End |
2011-01-13T15:23:31
|
Participant |
Robert Cerny
|
|
We are sorry
This page cannot be displayed in your browser. Use Firefox, Opera, Safari, or Chrome instead.