Computer Audio Asylum

Pagefile, threads handles size

60.242.40.107

erin

In Reply to: RE: cPlay - the open source high-end audio player using ASIO posted by cics on May 05, 2008 at 13:31:58

Hello Gents,

Just wondering if those who have "highly tweaked" operating systems would be kind enough to post their Pagefile size, threads and handles as displayed in task manager upon CMP startup. I think this would help myself and others determine how far we have to go to improve our systems.
Thanks.

Follow Ups:

RE: Pagefile, threads handles size - theob 06:18:28 01/30/12 (3)
Would give you that if I wasn't so 'highly tweaked' that I dont have that functionality any more. In the absence of that my tweaked windows xp system is 22 mb in size with config @ 0.52 mb in size. Not much left to do anything except/boot/play music.
- RE: Pagefile, threads handles size - erin 23:32:43 01/30/12 (1)
  Hi, yes that is what I was after. My stats are below:
  
  Pagefile = 25.5MB (before loading an album)
  Handles = 896
  Threads = 92
  Processes =11
  
  Still hoping to see some more responses from other people.
  I have noticed that every time I reduce handles and threads the sound gets better, without exception, but I am using a USB spdif converter.
  - RE: Pagefile, threads handles size - Ryelands 03:53:49 01/31/12 (0)
    I have noticed that every time I reduce handles and threads the sound gets better . . .
    
    Not every time in my case but generally I agree. Meanwhile, the linked piece helped me to understand what Task Manager is reporting. Sort of.
    - What Task Manager tells you (Open in New Window)
- RE: Pagefile, threads handles size - Ryelands 10:12:53 01/30/12 (0)
  I'm not so far down the road as Rick, Ted and others and can still launch Task Manager - see pix.
  
  Note that winvnc.exe is a "headless" control utility. It is believed (though, obviously, unverifiable) that Isass.exe and svchost.exe do not normally run when suspended in cMP's setup dialogue but are invoked by Task Manager. Well, it's what I like to believe.
  
  If I'm right, you're looking at five processes plus cMP & cPlay.
  
  As I do not like the sound of (and have had issues with) AWE-enabled pre-loading of music data into RAM, I don't know what figures are returned for cPlay when so used but, as you can see, cPlay clearly pre-loads data into RAM somehow or other regardless of setting. (You can also see this by looking at the networking tab.)
  
  The setup here is an Intel D510MO dual-core Atom mini-ITX board driving a USB-connected DAC without upsampling. Data from my main system, a slooooooow single-core Atom, are pretty similar but I can't show them as it no longer has TM access. When I could, the main difference was that CPU load was a bit higher, especially at the start of a track.
  
  Hope that's what you were after,
  
  Dave

Post a Followup:

FAQ

Post a Message!

Forgot Password?

Moniker (Username):
Password (Optional):
	Remember my Moniker & Password (What's this?) Eat Me
E-Mail (Optional):
Subject:

Message:	(Posts are subject to Content Rules)

Optional Link URL:
Optional Link Title:
Optional Image URL:
Upload Image:
E-mail Replies:	Automagically notify you when someone responds.

To view your new posting or follow-up, click on the RELOAD or REFRESH button on your browser.

This post is made possible by the generous support of people like you and our sponsors:

Atma-Sphere Music Systems, Inc.