Sage service mode

[OverClock]

Is there any benefit to running Sage in service mode when the Sage interface is always running? Is there a performance benefit to not running the service if the interface is running?

[GKusnick]

If the computer reboots for any reason, the service starts automatically at bootup, whether or not you're logged in.

There's also an argument that running the UI and playback engine in a different process means that any malfunction of those components won't impact the recording engine, as it would if you run them all in the same process. And if the service does crash, Windows can restart it automatically.

[rickgillyon]

But you can have a script running to restart the UI if it does crash. And I've found the extenders work better when not using service mode.

[sainswor99]

Originally Posted by rickgillyon

But you can have a script running to restart the UI if it does crash. And I've found the extenders work better when not using service mode.

I used to run the GUI (with script as rickgillyon suggested), but since I started running 6.1 (since the betas) and Java 1.6, I haven't noticed any difference between using the service vs the GUI. I think the service is the best way to go, but if you're having issues, there are alternatives.

Stu

[rickgillyon]

Originally Posted by sainswor99

I used to run the GUI (with script as rickgillyon suggested), but since I started running 6.1 (since the betas) and Java 1.6, I haven't noticed any difference between using the service vs the GUI.

I wouldn't argue with you, I've not re-tried Service mode since 6.1, just no longer see the point. My script keeps alive more than just Sage, so it suits me. Always try the different options, I guess...