large source occupying on myfinal composition

2010-07-15 Thread 胡海鹏 - Hu Haipeng
Hello,
  I finally finish my concert overture, which has just 250 measures, 34 pages. 
The compiling is a nightmare! When I used normal way, the computer turned into 
a circumstance like it was about to crash. Then I used Process Tamer, a small 
util program to reduce source wasting. At first, it's ok to do anything while 
compiling, but after 5 minutes, the computer again became very slow. Then I 
went away to listen to The Firebird. After its 45 minutes' music, Lilypond was 
still compiling. I checked the task manager, and found it first used around 
120M of RAM, but then continuous ascend to over 520M, and then fall to 330M, 
and up to 472... After another about 50 minutes, The score was at last ready. 
The whole process took about 110 minutes!!! I'd like to know why Lilypond 
should use such a large memory, since cpu is not taken too much (but instead, 
system idle process.exe took very large percent (up to 94%) of cpu). I think 
I must buy a Win7 machine with 4 core cpu and 8gb RAM, otherwise I can't write 
a piece like The Firebird, which will burn my current machine into dust :-)
Regards
Haipeng


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


Re: large source occupying on myfinal composition

2010-07-15 Thread Graham Percival
There are some attempts to optimize the speed; one simple patch
reduces the time required by something like 40%.  But you should
expect such problems from an unstable development version.

Cheers,
- Graham

On Thu, Jul 15, 2010 at 06:22:56PM +0800, 胡海鹏 - Hu Haipeng wrote:
Hello,
  I finally finish my concert overture, which has just 250 measures, 34
pages. The compiling is a nightmare! When I used normal way, the computer
turned into a circumstance like it was about to crash. Then I used Process
Tamer, a small util program to reduce source wasting. At first, it's ok to
do anything while compiling, but after 5 minutes, the computer again
became very slow. Then I went away to listen to The Firebird. After its 45
minutes' music, Lilypond was still compiling. I checked the task manager,
and found it first used around 120M of RAM, but then continuous ascend to
over 520M, and then fall to 330M, and up to 472... After another about 50
minutes, The score was at last ready. The whole process took about 110
minutes!!! I'd like to know why Lilypond should use such a large memory,
since cpu is not taken too much (but instead, system idle process.exe
took very large percent (up to 94%) of cpu). I think I must buy a Win7
machine with 4 core cpu and 8gb RAM, otherwise I can't write a piece like
The Firebird, which will burn my current machine into dust :-)
Regards
Haipeng
 
  --
 
A:uIeOuOD--oIIo/O *Aa.NOEIa:ONuC,?'ouA:Ei 1/4thAd--L-?

 ___
 lilypond-user mailing list
 lilypond-user@gnu.org
 http://lists.gnu.org/mailman/listinfo/lilypond-user


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


Re: large source occupying on myfinal composition

2010-07-15 Thread Neil Thornock
Not that this is very *helpful* but when I've had this situation, I
process the first half of the score separate from the second half,
adjusting page numbers if needed.  I had to do this with my orchestra
piece -- it ended up saving an hour of processing time!

On Thu, Jul 15, 2010 at 4:51 AM, Graham Percival
gra...@percival-music.ca wrote:
 There are some attempts to optimize the speed; one simple patch
 reduces the time required by something like 40%.  But you should
 expect such problems from an unstable development version.

 Cheers,
 - Graham

 On Thu, Jul 15, 2010 at 06:22:56PM +0800, 胡海鹏 - Hu Haipeng wrote:
    Hello,
      I finally finish my concert overture, which has just 250 measures, 34
    pages. The compiling is a nightmare! When I used normal way, the computer
    turned into a circumstance like it was about to crash. Then I used Process
    Tamer, a small util program to reduce source wasting. At first, it's ok to
    do anything while compiling, but after 5 minutes, the computer again
    became very slow. Then I went away to listen to The Firebird. After its 45
    minutes' music, Lilypond was still compiling. I checked the task manager,
    and found it first used around 120M of RAM, but then continuous ascend to
    over 520M, and then fall to 330M, and up to 472... After another about 50
    minutes, The score was at last ready. The whole process took about 110
    minutes!!! I'd like to know why Lilypond should use such a large memory,
    since cpu is not taken too much (but instead, system idle process.exe
    took very large percent (up to 94%) of cpu). I think I must buy a Win7
    machine with 4 core cpu and 8gb RAM, otherwise I can't write a piece like
    The Firebird, which will burn my current machine into dust :-)
    Regards
    Haipeng

      --

    A:uIeOuOD--oIIo/O *Aa.NOEIa:ONuC,?'ouA:Ei 1/4thAd--L-?

 ___
 lilypond-user mailing list
 lilypond-user@gnu.org
 http://lists.gnu.org/mailman/listinfo/lilypond-user


 ___
 lilypond-user mailing list
 lilypond-user@gnu.org
 http://lists.gnu.org/mailman/listinfo/lilypond-user




-- 
Neil Thornock, D.M.
The recent BYU Symphony Orchestra performance of Plutoids:
http://neilthornock.net/mp3s/plutoids.mp3
Assistant Professor of Music
Composition/Theory
Brigham Young University

___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


Re: large source occupying on myfinal composition

2010-07-15 Thread Urs Liska

And of course you make heavy use of \set Score.skipTypesetting = ##t ?
So you don't have to wait so often ...

Best
Urs

Am 15.07.2010 21:04, schrieb Neil Thornock:

Not that this is very *helpful* but when I've had this situation, I
process the first half of the score separate from the second half,
adjusting page numbers if needed.  I had to do this with my orchestra
piece -- it ended up saving an hour of processing time!

On Thu, Jul 15, 2010 at 4:51 AM, Graham Percival
gra...@percival-music.ca  wrote:
   

There are some attempts to optimize the speed; one simple patch
reduces the time required by something like 40%.  But you should
expect such problems from an unstable development version.

Cheers,
- Graham

On Thu, Jul 15, 2010 at 06:22:56PM +0800, 胡海鹏 - Hu Haipeng wrote:
 

Hello,
  I finally finish my concert overture, which has just 250 measures, 34
pages. The compiling is a nightmare! When I used normal way, the computer
turned into a circumstance like it was about to crash. Then I used Process
Tamer, a small util program to reduce source wasting. At first, it's ok to
do anything while compiling, but after 5 minutes, the computer again
became very slow. Then I went away to listen to The Firebird. After its 45
minutes' music, Lilypond was still compiling. I checked the task manager,
and found it first used around 120M of RAM, but then continuous ascend to
over 520M, and then fall to 330M, and up to 472... After another about 50
minutes, The score was at last ready. The whole process took about 110
minutes!!! I'd like to know why Lilypond should use such a large memory,
since cpu is not taken too much (but instead, system idle process.exe
took very large percent (up to 94%) of cpu). I think I must buy a Win7
machine with 4 core cpu and 8gb RAM, otherwise I can't write a piece like
The Firebird, which will burn my current machine into dust :-)
Regards
Haipeng

  --

A:uIeOuOD--oIIo/O *Aa.NOEIa:ONuC,?'ouA:Ei 1/4thAd--L-?
   
 

___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
   


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

 



   



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


Re: large source occupying on myfinal composition

2010-07-15 Thread Neil Thornock
Yes, I just put skipTypesetting at the end of whichever lines are
necessary and then comment/uncomment them as needed.  Very fast.

I should say, in response to Graham's comment, that I have noticed
this behavior on the stable version -- the only one I've used for some
time now.

On Thu, Jul 15, 2010 at 1:55 PM, Urs Liska lilyp...@ursliska.de wrote:
 And of course you make heavy use of \set Score.skipTypesetting = ##t ?
 So you don't have to wait so often ...

 Best
 Urs

 Am 15.07.2010 21:04, schrieb Neil Thornock:

 Not that this is very *helpful* but when I've had this situation, I
 process the first half of the score separate from the second half,
 adjusting page numbers if needed.  I had to do this with my orchestra
 piece -- it ended up saving an hour of processing time!

 On Thu, Jul 15, 2010 at 4:51 AM, Graham Percival
 gra...@percival-music.ca  wrote:


 There are some attempts to optimize the speed; one simple patch
 reduces the time required by something like 40%.  But you should
 expect such problems from an unstable development version.

 Cheers,
 - Graham

 On Thu, Jul 15, 2010 at 06:22:56PM +0800, 胡海鹏 - Hu Haipeng wrote:


    Hello,
      I finally finish my concert overture, which has just 250 measures,
 34
    pages. The compiling is a nightmare! When I used normal way, the
 computer
    turned into a circumstance like it was about to crash. Then I used
 Process
    Tamer, a small util program to reduce source wasting. At first, it's
 ok to
    do anything while compiling, but after 5 minutes, the computer again
    became very slow. Then I went away to listen to The Firebird. After
 its 45
    minutes' music, Lilypond was still compiling. I checked the task
 manager,
    and found it first used around 120M of RAM, but then continuous
 ascend to
    over 520M, and then fall to 330M, and up to 472... After another
 about 50
    minutes, The score was at last ready. The whole process took about
 110
    minutes!!! I'd like to know why Lilypond should use such a large
 memory,
    since cpu is not taken too much (but instead, system idle
 process.exe
    took very large percent (up to 94%) of cpu). I think I must buy a
 Win7
    machine with 4 core cpu and 8gb RAM, otherwise I can't write a piece
 like
    The Firebird, which will burn my current machine into dust :-)
    Regards
    Haipeng


  --

    A:uIeOuOD--oIIo/O *Aa.NOEIa:ONuC,?'ouA:Ei 1/4thAd--L-?




 ___
 lilypond-user mailing list
 lilypond-user@gnu.org
 http://lists.gnu.org/mailman/listinfo/lilypond-user


 ___
 lilypond-user mailing list
 lilypond-user@gnu.org
 http://lists.gnu.org/mailman/listinfo/lilypond-user







 ___
 lilypond-user mailing list
 lilypond-user@gnu.org
 http://lists.gnu.org/mailman/listinfo/lilypond-user




-- 
Neil Thornock, D.M.
The recent BYU Symphony Orchestra performance of Plutoids:
http://neilthornock.net/mp3s/plutoids.mp3
Assistant Professor of Music
Composition/Theory
Brigham Young University

___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user