Thanks Andrew. I'll be around to answer any questions anyone has. I've not tried out Andrew's packaged beta myself yet, but will be doing over the next day or two.
For those asking "What's bliss?" – it's a music management application designed to be run on a server. At the moment, it only manages album art.
I'm the programmer of bliss – fully automated music management – http://www.blisshq.com
I installed the bliss rpm (bliss version: 20100403) on my VortexBox Appliance and let it run on my music library. I find that after it has analyzed all the cover art in my library and has identified alternative cover art for all the albums, it still uses 30% to 98% of CPU time, as shown by top.
This seems excessive, since there really is nothing bliss has to do at this point. Is it continually rescanning my music library, looking for changes/additions? If so, I think this needs to be changed to reduce CPU usage.
I would prefer it to not constantly scan my music library, but instead adopt the approach used by SqueezeBox Server, where a rescan of the music library must be initiated by the user, or else by the VortexBox software sending a Rescan request to SqueezeBox Server over its API port.
I would like to see:
1. When bliss finishes processing the music library, it stops active scanning for new music requiring cover art, and goes into a quiescent state.
2. A Rescan music library button added to bliss.
3. An API interface so the VortexBox software can send a Rescan request to bliss.
This should reduce CPU usage of bliss when it has nothing to do.
As it stands now, I shut down the bliss daemon and only turn it on when I need it. This should not be necessary, but I have to do it since bliss is quite the CPU hog, even when my music library isn't changing, and I'm not using the bliss web interface.
Would lowering the Bliss process priority make any difference? My guess is that it would not help, because it would still use the balance of the CPU.
I guess the problem with high-percentage CPU use is that it draws more power, makes more heat, and runs the fan faster and more often to dump the heat. I have noticed the fan noise when the VBA is busy.
The main problem with bliss chewing up CPU cycles is that it takes them away from CD ripping and encoding, music library scanning by SqueezeBox Server, and any transcoding SBS has to do to stream music to various players.
I don't mind bliss using the CPU when it has something productive to do, but not if it's constantly scanning a non-changing music library.
First off, my questions are only intended to help me to understand Linux and VortexBox better.
1. If Bliss is now scanning the music collection constantly, it's probably running disk seeks constantly. That cannot be good for the drive. It that correct?
2. Would lowering Bliss's priority preserve CPU cycles for ripping, encoding, and SBS scanning and solve that problem?
I installed the bliss rpm (bliss version: 20100403) on my VortexBox Appliance and let it run on my music library. I find that after it has analyzed all the cover art in my library and has identified alternative cover art for all the albums, it still uses 30% to 98% of CPU time, as shown by top.
This seems excessive, since there really is nothing bliss has to do at this point. Is it continually rescanning my music library, looking for changes/additions? If so, I think this needs to be changed to reduce CPU usage.
Yep, that's way too much. Even on my home server when bliss is actually doing something it doesn't go above 50% much.
Regarding scanning: bliss does not scan, on Linux it uses inotify, a notification mechanism for file changes. This should mean it gets told about file changes which is more efficient, rather than rescanning to find them.
However, if bliss has finished its work and it's still using that much CPU there must be something wrong, so I want to solve this! A first step that would help me would be if you could send me your logs (/tmp/bliss.log.*)
This week I have been working on some performance/memory consumption improvements prompted by a customer who was having memory and CPU trouble (although on Windows). It turned out he had several directories with a lot ( > 100, some with ~400) of tracks inside, all from different albums. This caused high memory usage. I tracked down the issue and fixed it. This has been tested in his installation and will be released as a general beta this weekend. If you like, we could give it a whirl on your VortexBox.
I think your suggestions regarding a rescan button sound reasonable because some people may rather just work this way. Could you add it to the UserVoice page?
I'm the programmer of bliss – fully automated music management – http://www.blisshq.com
Ron pointed out to me by email that he'd noticed the CPU usage increased markedly when the web interface is open, and for a good while afterwards.
Having tested this in a number of ways, I agree. Having measured the usage by various parts of the application, I am working on some efficiencies that should hopefully lower this CPU usage.
I'll keep you posted on how things go.
I'm the programmer of bliss – fully automated music management – http://www.blisshq.com
I have installed Bliss but it doesnt work. I have included the install text which displays a problem with starting the deamon. I have tried starting manually to no avail. Is there anything i can do?
Thanks in advance.
[vortexbox.localdomain ~]# yum install bliss Setting up Install Process Resolving Dependencies –> Running transaction check —> Package bliss.i586 0:1.0-1 set to be updated –> Finished Dependency Resolution
I have installed Bliss but it doesnt work. I have included the install text which displays a problem with starting the deamon. I have tried starting manually to no avail. Is there anything i can do?
Login 
Register 
Search 
Home
Topic RSS 
