I currently have a AMD Sempron 140. Its more than enough power for a normal unraid system (low-wattage and cheap too). I was unable to unlock the second core 

 

I have Subsonic running on my unRaid. Streaming works great and navigation of the web interface is good. The last few weeks I've been trying to find a bottleneck when listing music folders with a large (800+) number of sub-folders. I'm working with the developer currently too. The whole program is in RAM and Joe L's dir_cache prevents the drives from spinning up so I would think it would be super fast. It's not the JRE for sure. What I have noticed was the CPU is pegged the whole time while the list is built.

 

I overclocked my CPU to 3510mhz and it cut the time almost in half (2min 20sec instead of 4:27), but this is still kind of sluggish in my opinion (and I have larger music folders). I really need this application to work well so I'm considering purchasing a dual-core.

 

I like the AMD Phenom II X2 550 Black Edition Callisto 3.1GHz because of the 6meg L3 cache. The 80watt and $102 price is not so great, but its received hundreds of great reviews. I might wait a month and maybe it will go down in price.

 

The AMD Athlon II X2 250 Regor 3.0GHz is still a pretty low-watt CPU and the price is reasonable.

 

The later versions of unRAID do support dual core.

 

Changes from 4.3.3 to 4.4-beta1

 

    * New feature: support SMP (multi-core processors).

I like the AMD Phenom II X2 550 Black Edition Callisto 3.1GHz becuase of the 6meg L3 cache. The 80watt and $102 price is not so great, but its recieved hundrends of great reviews. I might wait a month and maybe it will go down in price.

 

The Phenom II 550BE is rated at 80W but actually uses closer to 65W. I have one in my HTPC and it doesnt use any more power than the same system with a Athlon 250 in it.

I've noticed the same behaviour, it happens when accessing disk shares, if i access the same resource, via a user share it is near instant.

 

Likewise if i access it directly. Start, run, \\server\diskx\share is near instant access. \\server\diskx then browsing to the same share causes high cpu, and a delay whilst file + folder list is generated. Most noticable with folders with large #s files or folders.

 

I assume user shares are cached wheras disk shares arent.

 

For your issue it might be easier to setup a user share for your music folder so that it gets cached.

 

Kaygee, accessing the disk directly (/mnt/disk2/Movies) made no difference.

 

The "shfs" process is the one that spikes during the listing process. The developer had this to say..