OLA Performance Stats - Revision history

Nomis52 at 01:17, 29 February 2012

2012-02-29T01:17:16Z

Nomis52 at 02:08, 14 August 2011

2011-08-14T02:08:16Z

Nomis52 at 19:03, 27 March 2010

2010-03-27T19:03:52Z

Nomis52 at 03:33, 27 March 2010

2010-03-27T03:33:59Z

Nomis52 at 03:32, 27 March 2010

2010-03-27T03:32:17Z

66.92.11.32 at 02:57, 27 March 2010

2010-03-27T02:57:56Z

66.92.11.32: Created page with 'This is a brain dump of random OLA performance metrics. Unless otherwise mentioned these were performed on a MacBook Pro 2.4GHz Intel Core 2 Duo === Idle Test === Receiving…'

2010-03-27T02:55:07Z

Created page with 'This is a brain dump of random OLA performance metrics. Unless otherwise mentioned these were performed on a MacBook Pro 2.4GHz Intel Core 2 Duo === Idle Test === Receiving…'

New page

This is a brain dump of random [[OLA]] performance metrics. Unless otherwise mentioned these were performed on a MacBook Pro 2.4GHz Intel Core 2 Duo

=== Idle Test ===

Receiving an Streaming DMX update for a non-active universe with 512 channels is 40-50uS. This represents the best-case turn around time for an RPC.

=== UsbPro Test ===

Patching the Usb Pro Output port causes the average loop time to increase to 150uS for a 512 channel packet. 200 frames/second is about the upper limit the Usb Pro can support.

=== E1.31 Test ===

Patching an E1.31 Output Port results in a loop time of 125uS @ 200fps. OLA can sustain at least 2200 frames per second in this mode, where the loop time drops to 70uS. This was tested with a single universe and 4 universes.

=== RPC Throughput ===

=== TODO ===

The average isn't the best measurement, we should use the working time for just dmx queries.

← Older revision		Revision as of 01:17, 29 February 2012
Line 1:		Line 1:
	This is a brain dump of random [[OLA]] performance metrics. Unless otherwise mentioned these were performed on a MacBook Pro 2.4GHz Intel Core 2 Duo . More general information is at [[Pipe vs Unix Socket Performance]]		This is a brain dump of random [[OLA]] performance metrics. Unless otherwise mentioned these were performed on a MacBook Pro 2.4GHz Intel Core 2 Duo . More general information is at [[Pipe vs Unix Socket Performance]]
		+
		+	Data can be gathered with [[ola_mon]]

	=== Idle Test ===		=== Idle Test ===

← Older revision		Revision as of 02:08, 14 August 2011
Line 1:		Line 1:
−	This is a brain dump of random [[OLA]] performance metrics. Unless otherwise mentioned these were performed on a MacBook Pro 2.4GHz Intel Core 2 Duo	+	This is a brain dump of random [[OLA]] performance metrics. Unless otherwise mentioned these were performed on a MacBook Pro 2.4GHz Intel Core 2 Duo . More general information is at [[Pipe vs Unix Socket Performance]]

	=== Idle Test ===		=== Idle Test ===

@@ Line 15: / Line 15: @@
 === Arduino RGB Mixer ===
-This can only do about 22 full frames per second.
+This can only do about 22 full frames per second. The loop time increases to 2000uS.
 === RPC Throughput ===

← Older revision		Revision as of 03:32, 27 March 2010
Line 12:		Line 12:

	Patching an E1.31 Output Port results in a loop time of 125uS @ 200fps. OLA can sustain at least 2200 frames per second in this mode, where the loop time drops to 70uS. This was tested with a single universe and 4 universes.		Patching an E1.31 Output Port results in a loop time of 125uS @ 200fps. OLA can sustain at least 2200 frames per second in this mode, where the loop time drops to 70uS. This was tested with a single universe and 4 universes.
		+
		+	=== Arduino RGB Mixer ===
		+
		+	This can only do about 22 full frames per second.

	=== RPC Throughput ===		=== RPC Throughput ===

@@ Line 20: / Line 20: @@
 === RPC Throughput ===
-At least 12k rpcs/second.
+The maximum with no ports/clients patched is around 20k rpcs/sec. At this point olad isn't reading the data fast enough and the socket buffers fill up and we losing framing.
 === TODO ===
 The average isn't the best measurement, we should use the working time for just dmx queries.