2013-06-18, 02:00
This is the monitoring tool during like 4 consecutive manual library updates: http://imgur.com/6coFHKQ The CPU never went over 51% and the Memory held remarkably steady (maybe a little too steady) at 29%. Should I be concerned by how much of the memory is cached?
Nothing seems to be testing the limits of my NAS, but still if I look at processes (they are mostly generically named like java and python), one of the python process's seems to consistently use 25% of my cpu. See here: here: http://imgur.com/Kquupo4 and here: http://imgur.com/yeMXSdv
On another possibly (but hopefully not) unrelated note, while I was running the manual updates to see what the Synology Monitoring tool would turn up I was keeping a very close eye on the debug log. Here: http://pastebin.com/kybzd1eK at line 648 there's, for example, this:
I hit Update Library, nearly instantly when I pulled up the context menu. and I tried it a few more times, this "DEBUG: Suspended the Sink" shows up precisely 10 secs after I initiate a manual Library Update and while xbmc is "frozen". And this appears to happen every time. I click Manual Update, 10 seconds later it prints Suspended the sink and then 25-40 seconds later the Library update starts.
I've asked before but never really gotten an answer, what is this sink thats being suspended?
Nothing seems to be testing the limits of my NAS, but still if I look at processes (they are mostly generically named like java and python), one of the python process's seems to consistently use 25% of my cpu. See here: here: http://imgur.com/Kquupo4 and here: http://imgur.com/yeMXSdv
On another possibly (but hopefully not) unrelated note, while I was running the manual updates to see what the Synology Monitoring tool would turn up I was keeping a very close eye on the debug log. Here: http://pastebin.com/kybzd1eK at line 648 there's, for example, this:
Code:
18:24:02 T:2564 DEBUG: ------ Window Deinit (DialogContextMenu.xml) ------
18:24:12 T:9132 DEBUG: Suspended the SinkI hit Update Library, nearly instantly when I pulled up the context menu. and I tried it a few more times, this "DEBUG: Suspended the Sink" shows up precisely 10 secs after I initiate a manual Library Update and while xbmc is "frozen". And this appears to happen every time. I click Manual Update, 10 seconds later it prints Suspended the sink and then 25-40 seconds later the Library update starts.
I've asked before but never really gotten an answer, what is this sink thats being suspended?
