5 Mar
2009
5 Mar
'09
3:15 a.m.
Thanks Gentlemen, lots of food for thought in your suggestions and
questions.
I'm definitely interested in building a 'vanilla' OS, stripped down to be as
lean as possible.
The swapoff command i didn't know about, so i'll have a look at that. That
may well be sufficient, but i'll test it, and see what happens.
Joel, i don't have problems with the regular setup, i'm just aiming for the
leanest, most efficient, stable setup i can get. You may well be right, that
what i have is close to ok now, and could just benefit from a tweak or two
here and there.
Julien, i've taken notes from your ideas. I like the idea of a text only
based OS for LS, as i use this now for opening regular templates. Makes
sense to me getting rid of cpu munching possibilities of a gui, and just
work at the most efficient interface possible.
James, i'd need to go through the processes i don't need, but having disks
as read only makes sense to me. I've already got two dedicated sample disks
that i keep scrupulously clean that are pretty well read only in my natural
workflow, so the 'habit' is already embedded.
Again, thanks fellas. This sort of info is highly useful for me, and
possibly others.
Alex.
On Thu, Mar 5, 2009 at 2:45 AM, Joel Roth <joelz(a)pobox.com> wrote:
On Thu, Mar 05, 2009 at 12:07:57AM +0300, alex stone
wrote:
--
Parchment Studios (It started as a joke...)
I have a question about running linux in ram.
The Scenario.
I'm researching building a dedicated Lsampler box, running headless, with
netjack doing the ins and outs.
Given the usually large templates i run (full orchestra), including a lot
of
articulations, i'm wondering how feasible it
would be to build a
barebones
Linux OS, with linuxsampler as the sole app, more
or less, (and required
libs, etc...), and run the entire thing in ram, that is, the OS,
Lsampler,
and samples.
Is this possible, and if someone's already tried this in some form or
other
successfully or otherwise, could you share some
experiences, pros and
cons,
etc... ?
I would be doing all this in Linux 64bit, if it has some decent
advantages.
Are you running into problems with a conventional setup?
Generally Linux pages whatever you need into RAM, and
anything that isn't used much gets swapped out. So without
doing anything, you might already be close to a
configuration that will work for you.
The leads me to suggest doing the job the vanilla way, then
adding optimizations incrementally to improve performance
to what you need.
I don't think that going headless, in itself, will give
you any benefits as far as your system's memory use.
AFAIK, you don't need to strip down your environment, as
having all the development tools and coveniences on disk
won't affect your memory consumption.
Joel
Alex.
--
Parchment Studios (It started as a joke...)
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
--
Joel Roth
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user