[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Server question: SSD or HDD ?

From: Mike Blackstock
Subject: Re: Server question: SSD or HDD ?
Date: Thu, 29 Jul 2021 15:15:12 -0400

Thanks Phil and David!

I got the 500 gig SSD option; I can always add more later. The entire Mutopia repository,
which I've cloned, with mp3s of all midi files added, is less than 10 gigs. 500 gigs is a lot!
I'll be sure to keep it under 70% capacity.

System specs are here:
They're putting it together right now. I opted for Ubuntu 20. It's dedicated,  just my lilypond projects.

Thx for checking the website page David.


On Thu, Jul 29, 2021 at 11:51 AM David Wright <> wrote:
On Thu 29 Jul 2021 at 15:01:58 (+0100), Phil Holmes wrote:
> On 29/07/2021 14:55, Mike Blackstock wrote:
> > I'm getting a new server for online hosting of lilypond stuff.
> >
> > I'm not much of a hardware guy... within my hosting budget, I can
> > have either a 500 GB SDD, or a 1 TB HDD pn the system I'll
> > be leasing.
> >
> > I've never had a system with a solid state drive... would it
> > be noticeably faster for compiling lilypond scores?
> >
> > <>
> Lilypond is pretty much CPU limited, so the speed of the drive has almost no effect on compiling scores.  It's also single threaded, so the best option for speeding it up is an ultra-fast single core CPU - if one exists these days.

OTOH the website reference in your signature implies that
several people could be simultaneously compiling their own
scores within IDEs, others downloading scores, consulting
documentation, and so on.

With most machines now offering several CPUs and cores,
I'd certainly expect the SSD option to be far faster.
But bear in mind that they do slow down when run near
full capacity. I've read recommendations that you
shouldn't exceed about 70% to maintain top speed, so
I would check your total storage requirements on the site.

Running near full capacity also impacts lifetime, but as
you're leasing, I guess that's of no concern to you.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]