Tags:
create new tag
view all tags

SID-02391: Hardware to Improve Performance

Status: Asked Asked TWiki version: 6.0.1 Perl version: 5.10.1
Category: CategoryPerformance Server OS: Centos 6.5 Last update: 7 years ago

I've done some benchmarking using different pieces of hardware to try and understand how the performance of TWiki can be improved but have run into a bit of a puzzle. I'm wondering if anyone could help me understand what I'm seeing.

We use TWiki to mange our drawing approval process, and our drawing web has roughly 2000 topics that we look up using SEARCH{}.

My initial thinking was that using a solid state drive would improve the performance, so I tested out the theory on a laptop. I tried a total of four scenarios, two were done using the TWiki 6.0.1 VM, using Virtualbox on Windows 10, with our Drawing Web contents added to (/pub and /data). The last two scenarios were done on an installation of Centos 6.5 (no virtualization). All scenarios were performed on the same laptop with only the HDD or SSD swapped out (formatted prior to each scenario to try to keep things as "clean" as possible). The laptop had the following specs: i7-3639QM @ 2.4GHz, 8 gig DDR3, Quadro K2000M (2 gigs). I ran Chrystal Disk Mark (Windows 10) on the HDD and SSD and the results were:

Test HDD Read [MB/s] HDD Write [MB/s] SSD Read [MB/s] SSD Write [MB/s]
Seq Q32T1 109.6 115.7 545.9 488.9
4KiB Q8T8 1.011 1.009 305.5 334.7
4KiB Q32T1 1.111 0.968 188.6 160.5
4KiB Q1T1 0.382 0.683 26.76 52.33

I don't fully understand the results, but I would believe that the performance of the SSD is significantly better than the HDD.

Now on to the benchmarking results. The times are the result of SEARCH{} on the Drawing Web.

Environment VM Specs HDD SSD
Windows 10 (clean install) 4 CPU cores with 100% execution cap
5 gigs ram
128 megs graphics
11.99s 10.87s
CentOS 6.5 (clean install) - 12.97s 12.41s

Looking at top, when the SEARCH{} was running, one core was at 100% (user: apache, command: view).

I was a bit puzzled so I also benchmarked grep, specifically '''time grep –rnw ‘/var/www/twiki/data/’ –e ‘Extrusion’''', and got the following results.

Environment VM Specs HDD SSD
Windows 10 (clean install) 4 CPU cores with 100% execution cap
5 gigs ram
128 megs graphics
11.773s 13.625s
CentOS 6.5 (clean install) - 34.161s 3.737s

As I mentioned, the results were not what I expected. I thought to try some further testing on a more powerful laptop. Xenon E-2176M @ 2.7 GHz, 32 GB ram, Radeon Pro WX 7100 (8 gig), SSD drive, using Virtualbox in Windows 10.

VM Specs Load Time (s)
4 CPU cores with 100% execution cap
5 gigs ram
128 megs graphics
11.38s
6 CPU cores with 100% execution cap
24 gigs ram
128 megs graphics
11.37s

Would anyone have any insights into the results I'm seeing? I know that there are some software options to try and improve the speed of TWiki however the server hardware we're using is from 2012 and we are considering an upgrade. The challenging part is that I can't seem to pinpoint why I'm unable to show any kind of performance increase in my tests with "different" (either physical or virtualized) hardware.

Please feel free to ask any questions on my method or anything I've left out and I'll happily try to answer.

-- Jani Hamalainen - 2019-02-19

Discussion and Answer

      Change status to:
ALERT! If you answer a question - or someone answered one of your questions - please remember to edit the page and set the status to answered. The status selector is below the edit box.
SupportForm
Status Asked
Title Hardware to Improve Performance
SupportCategory CategoryPerformance
TWiki version 6.0.1
Server OS Centos 6.5
Web server Apache 2.2.15
Perl version 5.10.1
Browser & version Chrome 72.0.3626.109
Edit | Attach | Watch | Print version | History: r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r2 - 2019-02-19 - JaniHamalainen
 
  • Learn about TWiki  
  • Download TWiki
This site is powered by the TWiki collaboration platform Powered by Perl Hosted by OICcam.com Ideas, requests, problems regarding TWiki? Send feedback. Ask community in the support forum.
Copyright © 1999-2026 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.