something funyn abuot the conf-file:

DJ AmAdEuS · 9th September 2003, 20:34

read this section of sc-conf carefully:
; Sleep defines the granularity of the client threads for sending data.
; DNAS 1.7.0, per client thread, will send up to 1,024 bytes of data
; per socket (or less depending on the window available), and then
; sleep for the provided duration before repeating the whole process.
; Note that making this value smaller will vastly increase CPU usage on
; your machine. Increasing reduces CPU, but increasing this value too far
; will cause skips. The value which seems most optimal for 128kbps
; streaming is 833 (833 microseconds per client poll) on our test labs.
; We wouldn't recommend setting it any lower than 100, or any higher than
; 1,024. If you have a slower machine, set this number lower to fix
; skips.
; Default value is 833.
; Sleep=833

wouldn't this mean that 128Kbit/s is impossible? i mean if the server sends 1024Bytes (1KB) to a client and then need to wait @ least 100ms, i could only send up to 10KB/s to the client....
I'm curious how these testers wanna have transfered 128KBit/s with a sleep-time of 833

DJ AmAdEuS · 9th September 2003, 20:35

'n btw, why is there such a little max-window set?

DJ AmAdEuS · 9th September 2003, 20:40

naother "btw": after setting this thing to 50ms my 128Kbit/s stream runs quite fine, and i don#t see this enourmous cpu-usuage they mention in their comment....

9th September 2003, 20:34	#1
DJ AmAdEuS Junior Member Join Date: Sep 2003 Posts: 8	something funyn abuot the conf-file: read this section of sc-conf carefully: ; Sleep defines the granularity of the client threads for sending data. ; DNAS 1.7.0, per client thread, will send up to 1,024 bytes of data ; per socket (or less depending on the window available), and then ; sleep for the provided duration before repeating the whole process. ; Note that making this value smaller will vastly increase CPU usage on ; your machine. Increasing reduces CPU, but increasing this value too far ; will cause skips. The value which seems most optimal for 128kbps ; streaming is 833 (833 microseconds per client poll) on our test labs. ; We wouldn't recommend setting it any lower than 100, or any higher than ; 1,024. If you have a slower machine, set this number lower to fix ; skips. ; Default value is 833. ; Sleep=833 wouldn't this mean that 128Kbit/s is impossible? i mean if the server sends 1024Bytes (1KB) to a client and then need to wait @ least 100ms, i could only send up to 10KB/s to the client.... I'm curious how these testers wanna have transfered 128KBit/s with a sleep-time of 833

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Switch to Linear Mode Hybrid Mode Switch to Threaded Mode

9th September 2003, 20:35	#2
DJ AmAdEuS Junior Member Join Date: Sep 2003 Posts: 8	'n btw, why is there such a little max-window set?

9th September 2003, 20:40	#3
DJ AmAdEuS Junior Member Join Date: Sep 2003 Posts: 8	naother "btw": after setting this thing to 50ms my 128Kbit/s stream runs quite fine, and i don#t see this enourmous cpu-usuage they mention in their comment....