I notice this not only on Pd but on most programs... gnome-terminal eventually starting taking so long to start up the first couple of times that I gave up and started with xterm, for example. Firefox takes a long time as well and I am using that every day...
km
On 10/4/07, ild0012@londonmet.ac.uk ild0012@londonmet.ac.uk wrote:
On Wed, Oct 03, 2007 at 09:15:06AM -0700, Miller Puckette wrote:
Hmm, now has anyone noticed that Pd (first time after booting) starts up progressively more slowly over the months you own a linux machine? I'm suspicious that there's a correlation with how much software you have loaded on the machine. Maybe having lots of shared libraries and
programs
to use them makes dynamic linking slower (see, e.g., 'man ldconfig').
That's nothing but a guess.
cheers Miller
i think this is not what is happening really..
i noticed a slowdown when i added a huge bunch of externals with different paths to them. so now i removed all and set the nessary once in one locations but with subdirectories (by name, as appears in the cvs). this seems to be fine ..
i think that ldconfig caches frequently used stuff in /etc/ld.conf.cache but still keeps only file descriptors in the memory ..
On Thu, Oct 04, 2007 at 12:53:46AM +0100, Andy Farnell wrote:
Yes this is page/cache feature and seen with many apps. If you have a very frequently used app that you want to load fast each time then consider creating a RAM disk. Study Knoppix and Puredyne to see that in action. A start script to load Pd bins into RAM and then set the path to them. Useful for performance situations maybe.
On Wed, 03 Oct 2007 09:10:27 +0200 Atte Andr? Jensen atte.jensen@gmail.com wrote:
Hi
When I run pd the first time it takes a while to load, the second
time
it's much faster. I use a bash script to load my session (ardour,
muse,
pd + more) so if pd isn't running before muse, muse can't connect
it's
midi outs to pd's midi in.
I assume the load time is a matter of loading a binary, that's
cached
the second time. If so, where's the big binary? I tried running "cat /usr/local/bin/pd > /dev/null" in the beginning of my bash script,
but
that didn't seem to work.
If the above is a blind alley, whe could be done to speed up pd
loadtime
the first time?
NB: pd is version 0.40.3, and I'm running debian/linux...
-- peace, love & harmony Atte
http://atte.dk | http://myspace.com/attejensen http://anagrammer.dk | http://modlys.dk
PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
-- Use the source
PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list