Feature #1552
separate WebUI-backend from tvheadend
0%
Description
working on entries of automatic recorder will result in a frozen browser quite often or errors in chrome like the snapshot.
Looking at the backend machine, lots of timers have been created, but the CPU usage is about 25% or lower.
So I guess, the web-ui will become more responsive, if the save/refresh actions are not bound to the real actions of tvheadend like creating timers or the like.
The web-ui could i.e. create jobs on save, which the tvheadend-engine could process in a queue.
The web-ui should always deliver data snapshots, without waiting for any scheduled tasks.
Reinhard
Files
History
Updated by Adam Sutton almost 12 years ago
Updated by 
- Status changed from New to Rejected
I don't understand this as a feature request? There is an acceptable split between front/back end processing in my opinion, the mutexes that control access are frequently unlocked and should not cause excessive delays. There was a bug in some of the return values that meant the browser may have thought the server had not completed the request.
If you have specific examples of slow performance, please report that as a bug.
Adam