User Forum

We were looking through some of the trouble shooting parts of the manual for slow content server issues.  One of the items to check is the Binary Storage folder.  But it doesn't indicate what would be acceptable size.  We assumed this was the folder marked Binary Storage in the Axis TV Content Server folder.  Ours is currently at 133MB.  Does anyone else have experience with performance issues related to the folder size?  Or a recommendation on what size this should be or if it changes due to the number of channel players connected?  Any suggestions appreciated.  -Cassidy

Hi Cassidy, I run into occasional issues with my content server and i'm currently in the process of upgrading it to a dell. Without knowing any specs on your server or the amount of channel players you are pushing to i can give you a couple quick things to check out. 1. Do you backup? If how often do you do so and do you clean out your old backups. C:Axis Tv Bbackups 2. Do you use EMS? If so does your EMS create a ems.log file you may want to delete that log file and just recreate it so that the .vbs script starts logging again. A batch script written and scheduled to do this automatically would be helpful. C:Visix/AXIS TV Content services. 3.Make sure you don't have any runaway processes in the task manager. A quick re-boot of the server(aka network hiccup) will knock those loose. Hope i was able to help. Jim

JimB,

Thanks for the suggestions.  I'll get with my server guy and we'll give them a look.  We are running on a VM and have been told that might cause some issues but the machine has more than the minimum reqs so we're still looking for the underlying issue.  Thanks so much!

Hi.  We're running Content Server 7.0.14 on a virtual machine (VMware ESX 3.0.2).  We've applied 4 CPUs to the VM but still the web content is extremely slow, or times out all together, and the VM's cpu usage is constantly upwards of 90%.  We're serving content to about 500 users through our Intranet.  Any luck with figuring out if your slowness issue was VM related or Visix-config related?

Thanks,

t

It is good to see there are other VM users out there. Interesting you should ask about this now.  We were having problems with our services not restarting after reboot and after Javier did some looking around he discovered the services were timing out because SQL Server was so slow coming up.  Our server runs pegged out all the time and it takes about 15 minutes for the thing to reboot.  After Javier's discovery, one of our server admins got to looking at the specific error logs and eventually found a known issue on Microsoft's site about SQL Server 2005 that fit our symptoms.  http://support.microsoft.com/kb/937745  He found a patch but it wasn't for the Express version of SQL Server 2005.  He found a patch for express but it wasn't certified by Microsoft.  So, today he cloned the server so he can test the patch on the clone.  If it works he will apply the patch to the production server and hopefully we will all live happily ever after.  I will be sure and post findings as we test this.

 cp