Quote:
Originally Posted by hyperfilter
We second this. :)
|
What is this?
Advertisement as posts now?
Hey Hyper-filter ad-guy: advertising here by replying to a thread which has NOTHING to do with your services makes me NOT to chose your service.
By the way... Business running bad? You make your product look rather unprofessional and not wanted by making these "advertisement posts" on these forums. Congrats: you gained at least 1 person who will NOT try out or rent your services :)
Sorry for the off-topic here. I really had to say this.
All in all, I agree with Mega. From what I've seen in the server hosting scene, these files simply have an outdated architecture, and there's a lot of overhead going on between the modules.
Also regarding threads or non-threads -> It might be that the threading itself improves after each CPU generation coming out. But think that the development of new processors and "technologies" focus absolutely on multi-threaded computing! Nobody builds single-threaded applications anymore - so why should Intel/AMD stick develop and research costs into this, if this is a dead horse?
Regarding "ECC-RAM" bullshitbingo here: yeah, kinda every rent-server in the net runs on ECC ram, which is a must for in-memory databases for example. Do you know any server hoster who offers non-ECC ram? never saw one. Anyway - let me quote something real quick regarding ECC-Ram:
Quote:
ECC VS Non-ECC: Speed
According to tests, ECC RAM is slightly slower than non-ECC RAM. As claimed by many memory manufacturers, ECC memory is 2% slower than standard RAM because the additional time it takes for the system to check for any memory errors.
After testing the comparable CPUs (Intel Core i7 4771 3.5GHz Quad Core 8MB versus Intel Xeon E3-1275 V3 3.5GHZ Quad Core 8MB), we found that the estimate value 2% is roughly correct.
|
... So with ECC, the performance is even worse :)
Don't get me wrong - I'm a fan of ECC and I use it everywhere where I can use it. But ECC is not really an argument worth here, as these files run on any type of ram, and there aren't any non-ECC servers (physical or virtualized), unless it's that old crappy P4 Box which you had in your basement during the last 8 years.
What suddenly pops into my mind: maybe virtualizing that 1-threaded application, and let multiple physical cores work on that virtualized "wrapper" could be feasible? This is the only thing that pops into my mind as a workaround for these old single-threaded applications.
Laugh if you want :) Just brainstorming here what one could give a try to increase the "single thread computing performance" and v-wrap it :)