All,
Do you have experience with running Trinity on older hardware?
I have a PI and a PII. For years I ran KDE 3.5.10 on both. While hardly the fastest hardware, and 3.5.10 hardly the snappiest desktop environment, the system was usable. Trinity R14 on both systems is almost unusable. Starting Trinity takes a minute or two. Opening konsole takes 7-10 seconds. Opening a preloaded konqueror takes 20-25 seconds.
I realize free/libre software never truly supported older hardware despite claims otherwise and developers instead move relentlessly onward with bleeding edge hardware. Still, because of the many improvements I would think Trinity R14 would fare better, at least as good as 3.5.10.
Any ideas? Any help?
Darrell
There are only a few things to make an old system run faster:
- put in all the ram you can salvage from old equipment - disable swap. - replace the harddrive with some kind of solid state disk, e.g. cf-card + ide-adapter (I have two of these things in my "box of little things I probably will never use" - just drop a line if you need one)
Nik
Am Mittwoch, 4. Dezember 2013 schrieb Darrell Anderson:
All,
Do you have experience with running Trinity on older hardware?
I have a PI and a PII. For years I ran KDE 3.5.10 on both. While hardly the fastest hardware, and 3.5.10 hardly the snappiest desktop environment, the system was usable. Trinity R14 on both systems is almost unusable. Starting Trinity takes a minute or two. Opening konsole takes 7-10 seconds. Opening a preloaded konqueror takes 20-25 seconds.
I realize free/libre software never truly supported older hardware despite claims otherwise and developers instead move relentlessly onward with bleeding edge hardware. Still, because of the many improvements I would think Trinity R14 would fare better, at least as good as 3.5.10.
Any ideas? Any help?
Darrell
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
There are only a few things to make an old system run faster:
- put in all the ram you can salvage from old equipment
- disable swap.
- replace the harddrive with some kind of solid state disk, e.g. cf-card +
ide-adapter (I have two of these things in my "box of little things I probably will never use" - just drop a line if you need one)
Nik
Am Mittwoch, 4. Dezember 2013 schrieb Darrell Anderson:
All,
Do you have experience with running Trinity on older hardware?
I have a PI and a PII. For years I ran KDE 3.5.10 on both. While hardly the fastest hardware, and 3.5.10 hardly the snappiest desktop environment, the system was usable. Trinity R14 on both systems is almost unusable. Starting Trinity takes a minute or two. Opening konsole takes 7-10 seconds. Opening a preloaded konqueror takes 20-25 seconds.
I realize free/libre software never truly supported older hardware despite claims otherwise and developers instead move relentlessly onward with bleeding edge hardware. Still, because of the many improvements I would think Trinity R14 would fare better, at least as good as 3.5.10.
Any ideas? Any help?
Darrell
Please note that this might not be all TDE's fault. I have noticed that the X server (and possibly the kernel itself) tends to get slower and slower from release to release on old hardware. In general, locking myself to an old version of the kernel and Xorg on old hardware, then compiling new software on top of those old versions, seems to give halfway decent results.
However, if you are noticing that TDE is running slower than KDE 3.5.10 on the same X/kernel versions, then we have a problem. ;-)
Tim
On Wednesday 04 December 2013 06:21:46 you wrote:
All,
Do you have experience with running Trinity on older hardware?
I have a PI and a PII. For years I ran KDE 3.5.10 on both. While hardly the fastest hardware, and 3.5.10 hardly the snappiest desktop environment, the system was usable. Trinity R14 on both systems is almost unusable. Starting Trinity takes a minute or two. Opening konsole takes 7-10 seconds. Opening a preloaded konqueror takes 20-25 seconds.
I realize free/libre software never truly supported older hardware despite claims otherwise and developers instead move relentlessly onward with bleeding edge hardware. Still, because of the many improvements I would think Trinity R14 would fare better, at least as good as 3.5.10.
Any ideas? Any help?
Darrell
I uderstand the concepts of this thread, that said PI, PII, any box that sucks energy, do not need supporting, I know you have some :-) I have some, they run the software from the same era is great..which isn't all that usefull anymore for me. Firewalls and various services run ..but back to the 'to much energy use' issue.
At my LUG we used to reuse all sorts of older boxes, give them away. NO more. Energy consumption is a bigger part of the decision tree, smartphones are way more powerfull for what consumers want, business's will have newer hardware and the $$ to manage it.
YMMV, but as a project I would draw the support line closer to now.
On Wednesday 04 December 2013 06:21:46 you wrote:
All,
Do you have experience with running Trinity on older hardware?
I have a PI and a PII. For years I ran KDE 3.5.10 on both. While hardly the fastest hardware, and 3.5.10 hardly the snappiest desktop environment, the system was usable. Trinity R14 on both systems is almost unusable. Starting Trinity takes a minute or two. Opening konsole takes 7-10 seconds. Opening a preloaded konqueror takes 20-25 seconds.
I realize free/libre software never truly supported older hardware despite claims otherwise and developers instead move relentlessly onward with bleeding edge hardware. Still, because of the many improvements I would think Trinity R14 would fare better, at least as good as 3.5.10.
Any ideas? Any help?
Darrell
I uderstand the concepts of this thread, that said PI, PII, any box that sucks energy, do not need supporting, I know you have some :-) I have some, they run the software from the same era is great..which isn't all that usefull anymore for me. Firewalls and various services run ..but back to the 'to much energy use' issue.
At my LUG we used to reuse all sorts of older boxes, give them away. NO more. Energy consumption is a bigger part of the decision tree, smartphones are way more powerfull for what consumers want, business's will have newer hardware and the $$ to manage it.
YMMV, but as a project I would draw the support line closer to now.
-- Peace,
Greg
Well, you are very much correct on the watts/performance issue, I look at it this way. Your average PII/PIII is about as powerful as some of the ultra-efficient Arm-based SBC devices now available for Linux users. If TDE can run well on PII/PIII hardware, then it will likely run well on those very efficient Arm-based systems as well.
Tim