|
SageTV Beta Test Software Discussion related to BETA Releases of the SageTV application produced by SageTV. Questions, issues, problems, suggestions, etc. regarding SageTV Beta Releases should be posted here. |
|
Thread Tools | Search this Thread | Display Modes |
#1
|
|||
|
|||
Beta Client Lockup
Yes I did submit this in a Debug Report!!
Finally got Sage TV installed on two spare pc's so that I could test the Beta software. Problem is that the Sage client locks up on the PC running the service. The following was repeated over and over again in the debug window Fri 10/22 21:44:48.207 SageTV received connection from:Socket[addr=/127.0.0.1,po rt=42024,localport=1356] Fri 10/22 21:44:48.233 Connection lost from: Socket[addr=/127.0.0.1,port=42024,l ocalport=1356] by:java.io.IOException: You may NOT re-use the same SageTVClient license on more than one machine! Please vist http://sage.tv/buy.html to purchase an additional license key for th is client. Fri 10/22 21:44:48.245 Cleaning up c/s connection Fri 10/22 21:44:48.250 Error establishing server connection of:java.io.IOExcepti on: You may NOT re-use the same SageTVClient license on more than one machine! Please vist http://sage.tv/buy.html to purchase an additional license key for th is client. Fri 10/22 21:44:48.260 at sage.av.hq(Unknown Source) Fri 10/22 21:44:48.264 at sage.av.<init>(Unknown Source) Fri 10/22 21:44:48.267 at sage.ad.a(Unknown Source) Fri 10/22 21:44:48.275 at sage.ad.a(Unknown Source) Fri 10/22 21:44:48.278 at sage.SageTV.<init>(Unknown Source) Fri 10/22 21:44:48.282 at sun.reflect.NativeConstructorAccessorImpl.newInstance 0(Native Method) Fri 10/22 21:44:48.287 at sun.reflect.NativeConstructorAccessorImpl.newInstance (Unknown Source) Fri 10/22 21:44:48.292 at sun.reflect.DelegatingConstructorAccessorImpl.newInst ance(Unknown Source) Fri 10/22 21:44:48.297 at java.lang.reflect.Constructor.newInstance(Unknown Sou rce) Fri 10/22 21:44:48.302 at java.lang.Class.newInstance0(Unknown Source) Fri 10/22 21:44:48.305 at java.lang.Class.newInstance(Unknown Source) Fri 10/22 21:44:48.319 at sage.Sage.b(Unknown Source) Fri 10/22 21:44:48.322 NetworkClient fullCleanup null The specs on the PC acting as the server. Dell workstation 400 Dual pentium II 300MHZ, 416MB RAM, XP PRO SP2, MadDog Nvidia GeForce FX5200 PCI graphics card, 160GB HD with 100GB dedicated to Sage TV formatted with 64K sectors, IOMagic DL 16X DVD drive, 32 bit CompUsa Audio card, IOGear USB 2.0 PCI card. Hauppauge WinTV USB2. Specs on the client PC Dell Dimension 2400 2.4 Ghz Celeron 640MB Ram XP Home edition. All other options standard. Disabled and stopped most services based on information obtained from BlackViper. Installed PowerDVD, Newest Nvidia decoders, MoonLight evaulation decoders. I tweeked the machine to the max using SageTV 2.0 prior to installing the Beta RC5 version. I was able to get acceptable results viewing shows with this PC using (Encoding Good) by using the NVidia decoders, increasing the MPeg buffers to 512, removing all XP Visual Effects and disabling around 13 services. CPU usage was high but everything worked. This machine is not my main Sage TV pc and It was an interesting exercise to get Sage version 2.0 to run on it. I thought that the forum users would be interested in some Task Manager Info regarding the Beta software on this slow PC. Here are the numbers: Service Start Time 1:59 seconds PF Usage prior to service start 189MB After service start 239MB System CPU usage % prior to service start 2% to 12% System CPU usage during service start between 50% and 64%. Service CPU usage during start between 45% and 61% Avg 46% Service CPU usage during client connect from 2nd PC 41% to 51% Time to Main Menu on client pc 47 seconds. Recording shows. Service CPU usage Recording a show and not watching it on the client PC 2% to 4% (Encoding size GOOD) Service CPU usage Recording a show and watching it on the client PC 4% to 9% (Encoding size GOOD) Service CPU usage when the service is idle 0%. Service CPU usage Recording a show and watching it on the client PC 15% to 21% (Encoding Max Quality) Service Thread count between 26 and 33 threads. Service Mem Usage 46876K Based on these numbers I think Sage is heading in the right direction on this product release. I don't want to publish the 2.0 numbers for this machine in this particular forum but take my word for it I think the memory usage, thread count, and CPU utilization on this release are great improvements. I wish they could get some of the other numbers down maybe some creative caching is in order (Hint Hint) I will leave this setup in place for the next week and hope they get the license issue fixed. If any forum users can think of some tests they would like to to run on this setup just post it to the forum. I can't wait to install 2.1 on my main PC when it goes final. Main PC: Dual 2.8 GHZ Xeon, 1GB Ram, 2 200GB Hard Drives, Audigy 2 Platinum |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|