Results 1 to 10 of 10

Thread: Console output taking a lot of CPU cycles?!? [images: 190 KB]

  1. #1
    Member
    Join Date
    Apr 2002
    Location
    The Netherlands
    Posts
    47

    Arrow Console output taking a lot of CPU cycles?!? [images: 190 KB]

    I've just noticed that the process called "crss.exe" on my Windows 2000 machine will take up about 20-25% of my CPU cycles during "Tight Spot - Trying Alternate Conformation #number " calculations...and only then, not at any other moment that the client is running.

    Crss.exe is the process that controls the console output:

    "Client Server Runtime Subsystem, provides text window support, shutdown, and hard-error handling to the Windows NT environment subsystems."

    OK:

    - Am I the only one who experiences this?
    - 20% for displaying something.. isn't that a bit high? Perhaps just showing the message "Trying Alternate Confirmation" without the rapid counter next to it.. might just move those 20% back to the actual computation?

    Thinking out loud

    I'll add two screenshots:
    Attached Images Attached Images

  2. #2
    Member
    Join Date
    Apr 2002
    Location
    The Netherlands
    Posts
    47
    Second screenshot:
    Attached Images Attached Images

  3. #3
    Same here; the csrss process uses much more cpu time than the foldtrajlite does... (4 times more)

    I turned "Quiet Mode" on, this should help

  4. #4
    Senior Member
    Join Date
    Apr 2002
    Location
    Oosterhout, Netherlands
    Posts
    223
    This has always been the case. I think that during Phase I the load was even worse. Always use the -qt (quiet true) parameter. Improves your outpur a lot (don't forget the -rt for using extra RAM).
    Proud member of the Dutch Power Cows

  5. #5
    Member
    Join Date
    Apr 2002
    Location
    The Netherlands
    Posts
    47
    I can't recall that it was taking CPU cycles in the order of 20-25%..

    But now you're making me doubt again

    As far as I know it was always < 10% .. but I could be wrong

  6. #6
    Boinc'ing away
    Join Date
    Aug 2002
    Location
    London, UK
    Posts
    982
    I found this with the beta versions- the only way around it is to either run quiet or swtich to a non-MS OS

    (my usage was anywhere from 10 to 25% : )

    iirc - it's all down to MS's way of allowing command window output - as it has to emulate that takes CPU power...

  7. #7
    You can also run the DF client as a service to get around this issue.

    Jeff.

  8. #8
    Ill reduce the update frequency of that message for the next release
    Howard Feldman

  9. #9
    Junior Member
    Join Date
    Mar 2003
    Location
    Atlanta
    Posts
    5
    -qt mode worked like a charm. Muchas gracias!

    *scampers off to put three other win2k machines on quiet mode*

  10. #10
    Member
    Join Date
    Apr 2002
    Location
    The Netherlands
    Posts
    47
    Originally posted by Brian the Fist
    Ill reduce the update frequency of that message for the next release
    Thank you!

    Hopefully that will make life a bit easier for that MS service

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •