Tweet
I have Asset UPnP Server (version 3.0.0.1) running on a Windows XP box (SP3 and latest updates). It runs flawlessly (almost!) with my Arcam SoloNeo client. The XP box is dedicated to running as an Asset audio server. It has a hyper-threaded 3GHz CPU, and 4GB RAM (of which only about 3.4GB is usable by XP). My music files are stored in Apple Lossless format and transcoded by Asset into LPCM.
I had noticed that from time to time there are some minor pauses in the music output that last less than a second before the music carries on normally until it happens again some random time later (usually just a few minutes). I did a thorough investigation of the machine itself (using network and performance monitor tools) and found that hard paging seemed to be the problem. There was quite a high rate of hard page faulting being encountered. All other relevant metrics (network loading, CPU usage, disk queuing) were all well within the low-end of my expectations. I found the solution was to put my music files onto a separate and dedicated disk (away from the paging disk). Even though my problem has now gone away, I am curious about the hard paging rate. The "culprit" (from my analysis) is Asset-uPNP.exe which has about 40,000 hard pages faults for every 45 minutes of serving up music. I have more than enough RAM for hard paging not to be required. It may be that the program is set up to use no more than a certain amount of RAM. I have looked at the ini file (Asset-UPnPService.ini) but there appears to be no reference to RAM allocation there. Is there some way to increase the RAM usage and therefore cut down on the hard paging?
Thanks for your help.
I had noticed that from time to time there are some minor pauses in the music output that last less than a second before the music carries on normally until it happens again some random time later (usually just a few minutes). I did a thorough investigation of the machine itself (using network and performance monitor tools) and found that hard paging seemed to be the problem. There was quite a high rate of hard page faulting being encountered. All other relevant metrics (network loading, CPU usage, disk queuing) were all well within the low-end of my expectations. I found the solution was to put my music files onto a separate and dedicated disk (away from the paging disk). Even though my problem has now gone away, I am curious about the hard paging rate. The "culprit" (from my analysis) is Asset-uPNP.exe which has about 40,000 hard pages faults for every 45 minutes of serving up music. I have more than enough RAM for hard paging not to be required. It may be that the program is set up to use no more than a certain amount of RAM. I have looked at the ini file (Asset-UPnPService.ini) but there appears to be no reference to RAM allocation there. Is there some way to increase the RAM usage and therefore cut down on the hard paging?
Thanks for your help.
Comment