Re: [Mjpeg-users] 18 hours to encode 2 hours

2003-06-02 Thread Steven M. Schultz
hi! > From: [EMAIL PROTECTED] > Here's a script I've used - I use ssh only to set up "hose" on the > other machine, and both machines share a common filesystem over NFS. > Here yuv4mpeg2 data flows over the netpipe, and the (much smaller) > mpeg2 data flows back over NFS. I was thinking o

Re: [Mjpeg-users] 18 hours to encode 2 hours

2003-06-02 Thread scholnik
> From: [EMAIL PROTECTED] > I use netpipes instead of rsh, but either way the network shouldn't be I gave netpipes a try - worked "ok" but I couldn't find a way to pass parameters thru to the remote process. Easy to set up a shell

Re: [Mjpeg-users] 18 hours to encode 2 hours

2003-06-02 Thread Steven M. Schultz
Hi - > From: [EMAIL PROTECTED] > I use netpipes instead of rsh, but either way the network shouldn't be I gave netpipes a try - worked "ok" but I couldn't find a way to pass parameters thru to the remote process. Easy to set up a shell script of course. > much of a bott

Re: [Mjpeg-users] 18 hours to encode 2 hours

2003-06-01 Thread Bernhard Praschinger
Hallo > Question is, has anyone tried to "rsh" some jobs out to other > computers (e.g. on a 100Mb ethernet) to try to shorten the time, > or would that just mean the network becomes the bottleneck? > > I use netpipes instead of rsh, but either way the network shouldn't

Re: [Mjpeg-users] 18 hours to encode 2 hours

2003-06-01 Thread scholnik
Question is, has anyone tried to "rsh" some jobs out to other computers (e.g. on a 100Mb ethernet) to try to shorten the time, or would that just mean the network becomes the bottleneck? I use netpipes instead of rsh, but either way the network shouldn't be much of a bo