I have installed Nimble Server on Rasberry Pi as per instructions provided on the site.
But I am not even able to play 1 single mp4 video from a Android mobile client. Video stutters a lot, same video when loaded through Nimble on Windows work absolutely fine.
Dashboard of Nimble Streamer show 1% CPU load & 2% RAM load on RPi so its not overburdened. I am unable to figure out whats making it work in such sluggish manner.
Any help would be greatly appreciated...
You say you tried it on Android client. This might be bandwidth issue of your network.
Please try playing it on PC and measure the download speed to compare it to your mobile network capacity.
Thanks for your response, somehow things have improved now. I am able to play on 4 devices without any issue. On adding 5 devices things start to crawl.
 Only thing I could notice was that memory of RPi goes upto 921708 of 947732, maybe this is prohibiting more users to gain access. Is there anything that can be done to reduce this memory consumption ?
 Is there a Jessie upgrade version ? I have Whizzy at the moment ?
if your PI transmux mp4 -> hls it require enough disk IO and some memory. I'm recommend to increase RAM cache in server settings for prevent Nimble from using your ROM for hls chunk cache.
you can check PI with live stream and same users and if works your problem is in ROM speed for sure
Thanks for your response, I have made the following changes. Retesting now...
#max_cache_size = 64
max_cache_size = 80
#max_disk_cache_size = 4096
max_disk_cache_size = 6000
For Live stream I do not have Pi Camera yet :(
What I found that if I stop Nimble Streamer service the memory (RAM)is not de-allocated, I have to reboot to that. Could this be the problem resulting in video stuttering after 4 devices ?
response would be much appreciated, I would suggest keeping paid support option for customers genuinely interested in getting a response asap...
Please increase RAM/ROM cache via gui http://blog.wmspanel.com/2014/01/setting-nimble-caching-gui.html
config method will not work. it's obsolete
 Max RAM cache size(MB) from 80 to 320
 Max file cache size(MB) from 4000 to 16384
But still Nimble would serve just 6 connections which is the same as with earlier settings, no difference at all :(
These changes were done from the WMSPanel Web UI, not manually.
Nimble will not be able to serve more vod streams on PI then.
Try to use different transmuxer to compare or use server platform for your need.
It was not Nimble problem but Chrome that does not allow more than 6 connection to the same IP. I was able to overcome this and test on Firefox where it served almost 10 connections. Will be doing more stress testing tomorrow...