SliceScheduler is c00w's implementation, I never pushed mine out. The latest one looks like it might be working now. I implemented AltSliceScheduler as a variant of flower's original work. Will do some patches later this week to make it a little more aggressive, for now it's a moderately simple weighted time slicer.
Personally, I'm using that for now. Not sure what slice size works best, I think 600-900 is ok. With the getwork store, I find that it reduces stales and doesn't matter much if you hop around pools. Doesn't seem to make bitHopper send more getworks, so on the surface seems harmless? Didn't pay attention too much. The drawback is maybe sending the clients too many LPs?
Ed, does your SliceScheduler option work? Or is it only AltSliceScheduler that works for now? If not which is best to use?
I'm currently using altslice at 900, does that sound about right?