Performance Problems - Revision history

Behrooz at 11:35, 5 February 2020

2020-02-05T11:35:34Z

← Older revision		Revision as of 11:35, 5 February 2020
Line 81:		Line 81:
	*the video engine (e.g. MXWendler) runs also in 25 fps,		*the video engine (e.g. MXWendler) runs also in 25 fps,
	*the monitor has a refresh rate frequency of 50Hz.		*the monitor has a refresh rate frequency of 50Hz.

			{{#mpdftags: pagebreak}}

Behrooz: /* Monitors */

2020-02-05T11:34:33Z

Monitors

← Older revision		Revision as of 11:34, 5 February 2020
Line 78:		Line 78:
	=== Monitors ===		=== Monitors ===

	You cannot change the performance of your monitor, but you should take care that your whole system is in sync at a common base frame rate and refresh rate. ~~In Europe these~~ are ~~25/50 FPS at a 50Hz refresh rate:~~		Ideally, videos should be made in 30/60 frames per second and played on monitors or projectors with a 60Hz refresh rate. But this is not always the case, as for example, the fps and refresh rate standards vary in the UK, US, Europe and other parts of the world. You cannot change the performance of your monitor, but you should take care that your whole system is always in sync at a common base frame rate and refresh rate. So as an example, if your videos are rendered in 25fps, make sure that:
	*the video is rendered~~/produced~~ in ~~25/50 fps~~		*the video engine (e.g. MXWendler) runs also in 25 fps,
	*the video engine runs also in 25~~/50~~ fps		*the monitor has a refresh rate frequency of 50Hz.
	*the monitor has a refresh frequency of 50Hz

Behrooz: /* GPU */

2020-02-05T11:28:28Z

GPU

← Older revision		Revision as of 11:28, 5 February 2020
Line 67:		Line 67:
	::Antialiasing		::Antialiasing
	::Texture filtering		::Texture filtering
	*Use 'Single GPU Performance Mode' in combination with a ~~Matrox~~ to split the video output.		*Use 'Single GPU Performance Mode' in combination with a device to split the video output.
	*Be sure your Keystone setup ( in fact, this is geometry ) is not too complex for your graphics board.		*Be sure your Keystone setup ( in fact, this is geometry ) is not too complex for your graphics board.

Behrooz at 11:20, 5 February 2020

2020-02-05T11:20:25Z

← Older revision		Revision as of 11:20, 5 February 2020
Line 68:		Line 68:
	::Texture filtering		::Texture filtering
	*Use 'Single GPU Performance Mode' in combination with a Matrox to split the video output.		*Use 'Single GPU Performance Mode' in combination with a Matrox to split the video output.
	*Be sure your ~~keystone~~ setup ( in fact, this is geometry ) is not too complex for your graphics board.		*Be sure your Keystone setup ( in fact, this is geometry ) is not too complex for your graphics board.

	=== System Busses ===		=== System Busses ===

	Video data has to be carried from the disk to the cpu to the graphics card. At each stage, the video is decompressed, and the data stream will take more bandwidth. <br>		Video data has to be carried from the disk to the cpu to the graphics card. At each stage, the video is decompressed, and the data stream will take more bandwidth. <br>
	*Be sure that your disk bus is as fast as the disk. There is no point in connecting a fast RAID to USB 1.1.		*Be sure that your disk bus is as fast as the disk itself. There is no point in connecting a fast RAID to USB 1.1.
	*Always pair fast parts together, e.g fast memory ~~with~~ a fast mainboard.		*Always pair fast parts together, e.g use a fast memory on a fast mainboard.

	=== Monitors ===		=== Monitors ===

	*You cannot change the performance of your monitor, but you should take care that your whole system is in sync at a common base frame rate. In Europe ~~this is~~ 25 FPS:		You cannot change the performance of your monitor, but you should take care that your whole system is in sync at a common base frame rate and refresh rate. In Europe these are 25/50 FPS at a 50Hz refresh rate:
			*the video is rendered/produced in 25/50 fps
	** - the video is rendered/produced in 25 fps		*the video engine runs also in 25/50 fps
	** - the video engine runs in 25 fps		*the monitor has a refresh frequency of 50Hz
	** - the monitor has a refresh frequency of ~~75Hz~~

Behrooz at 11:06, 5 February 2020

2020-02-05T11:06:06Z

← Older revision		Revision as of 11:06, 5 February 2020
Line 51:		Line 51:
	*extreme large output sizes.		*extreme large output sizes.

			{{#mpdftags: pagebreak}}
	Am I GPU limited? <br>		Am I GPU limited? <br>

Line 61:		Line 62:
	::An image with a width of 1024 will be placed in a 1024 texture.		::An image with a width of 1024 will be placed in a 1024 texture.
	::An image with a width of 1025 will be placed in a 2048 texture.		::An image with a width of 1025 will be placed in a 2048 texture.
	*Try (at least) doubling the GPU RAM usage		*Try (at least) doubling the GPU RAM usage.
	*Under NVidia, for optimal performance, disable the following:		*Under NVidia, for optimal performance, disable the following:
	:Anisotropic filtering		::Anisotropic filtering
	:Antialiasing		::Antialiasing
	:Texture filtering		::Texture filtering
			*Use 'Single GPU Performance Mode' in combination with a Matrox to split the video output.
	* Use 'Single GPU Performance Mode' in combination with a Matrox to split the video output.		*Be sure your keystone setup ( in fact, this is geometry ) is not too complex for your graphics board.

	* Be sure your keystone setup ( in fact, this is geometry ) is not too complex for your graphics board.

	=== System Busses ===		=== System Busses ===

	* Video data has to be carried from the disk to the cpu to the graphics card. At each stage, the video is decompressed, and the data stream will take more bandwidth.		Video data has to be carried from the disk to the cpu to the graphics card. At each stage, the video is decompressed, and the data stream will take more bandwidth. <br>
	** - be sure that your disk bus is as fast as the disk. There is no point in connecting a fast RAID to USB 1.1		*Be sure that your disk bus is as fast as the disk. There is no point in connecting a fast RAID to USB 1.1.
	** - Have fast memory ~~and~~ a fast mainboard. ~~Mac Pro is a reference design in that area.~~		*Always pair fast parts together, e.g fast memory with a fast mainboard.

	=== Monitors ===		=== Monitors ===

Behrooz: /* GPU */

2020-02-05T10:58:56Z

GPU

← Older revision		Revision as of 10:58, 5 February 2020
Line 61:		Line 61:
	::An image with a width of 1024 will be placed in a 1024 texture.		::An image with a width of 1024 will be placed in a 1024 texture.
	::An image with a width of 1025 will be placed in a 2048 texture.		::An image with a width of 1025 will be placed in a 2048 texture.
	*( at least ) doubling the GPU RAM usage		*Try (at least) doubling the GPU RAM usage
	*Under NVidia, for optimal performance, disable the following:		*Under NVidia, for optimal performance, disable the following:
	:Anisotropic filtering		:Anisotropic filtering
Line 69:		Line 69:
	* Use 'Single GPU Performance Mode' in combination with a Matrox to split the video output.		* Use 'Single GPU Performance Mode' in combination with a Matrox to split the video output.

	* Be sure your keystone setup ( in fact, this is geometry ) is not too complex for your graphics board.		* Be sure your keystone setup ( in fact, this is geometry ) is not too complex for your graphics board.

	=== System Busses ===		=== System Busses ===

Behrooz at 10:55, 5 February 2020

2020-02-05T10:55:21Z

← Older revision		Revision as of 10:55, 5 February 2020
Line 59:		Line 59:
	*A solution may be to rework your visual setup.		*A solution may be to rework your visual setup.
	:Use only the resolutions you need, and keep resolutions below certain limits, especially Power-Of-Two limits.		:Use only the resolutions you need, and keep resolutions below certain limits, especially Power-Of-Two limits.
	::An image with a width of 1024 will be placed in a 1024 texture		::An image with a width of 1024 will be placed in a 1024 texture.
	::An image with a width of 1025 will be placed in a 2048 texture,		::An image with a width of 1025 will be placed in a 2048 texture.
	*( at least ) doubling the GPU RAM usage		*( at least ) doubling the GPU RAM usage
	*Under NVidia, for optimal performance, disable the following:		*Under NVidia, for optimal performance, disable the following:

Behrooz at 10:54, 5 February 2020

2020-02-05T10:54:14Z

← Older revision		Revision as of 10:54, 5 February 2020
Line 24:		Line 24:
	=== RAM ===		=== RAM ===

	Enough fast RAM is very important for MXW. Normally ~~computers~~ systems have enough RAM ( more than 8gb ) today, so this is generally not a likely source for performance problems.		Enough fast RAM is very important for MXW. Normally computer systems have enough RAM ( more than 8gb ) today, so this is generally not a likely source for performance problems.

	=== CPU ===		=== CPU ===
Line 38:		Line 38:
	:*Or play a movie ( ideally with sound ) and while it is playing, constantly open and close other clips. If the first movie starts jittering, you are CPU limited. <br>		:*Or play a movie ( ideally with sound ) and while it is playing, constantly open and close other clips. If the first movie starts jittering, you are CPU limited. <br>
	Solution		Solution
	*The solution is to get a faster CPU ( where MHz are in this case more important than the number of cores ) or - most of the times easier - reduce server load, eg. split videos, combine outputs, reduce resolutions, etc.		*The solution is to get a faster CPU (where MHz are in this case more important than the number of cores) or - most of the times easier - reduce server load, eg. split videos, combine outputs, reduce resolutions, etc.

	=== GPU ===		=== GPU ===
Line 44:		Line 44:
	MXW renders 100% on the GPU, no pixel color is touched on the CPU side. <br>		MXW renders 100% on the GPU, no pixel color is touched on the CPU side. <br>
	The performance of GPUs varies widely, some GPUs have 4 pixels processors, some have 1000s. If you have a recent model ( bought since 2015 ), you should not experience much performance problems on the GPU side. But there are important limits, most notably GPU RAM. This means, the dedicated GPU RAM built onto the graphics device. If you run out of GPU RAM, there will be a severe performance loss. <br>		The performance of GPUs varies widely, some GPUs have 4 pixels processors, some have 1000s. If you have a recent model ( bought since 2015 ), you should not experience much performance problems on the GPU side. But there are important limits, most notably GPU RAM. This means, the dedicated GPU RAM built onto the graphics device. If you run out of GPU RAM, there will be a severe performance loss. <br>

	A lot of GPU RAM is used when there are:		A lot of GPU RAM is used when there are:
	*Many images open,		*Many images open,
Line 50:		Line 51:
	*extreme large output sizes.		*extreme large output sizes.

	Am i GPU limited? <br>		Am I GPU limited? <br>

	* GPU limitation is reached, when it takes very long time to open eg. dialog boxes.
	* Reduce the output size. Use less effects. Delete some images, delete some videos. If the performance rises, you are GPU and/or GPU RAM limited.
	* A solution may be to rework your visual setup.

	** ~~- use~~ only the resolutions you need		Test
	** - keep resolutions below certain limits, especially Power-Of-Two limits.		*GPU limitation is reached when it takes a very long time to open eg. dialog boxes.
			*Reduce the output size. Use fewer effects. Delete some images, delete some videos. If the performance rises, you are GPU and/or GPU RAM limited.
	* An image with a width of 1024 will be placed in a 1024 texture		Solution
	* An image with a width of 1025 will be placed in a 2048 texture,		*A solution may be to rework your visual setup.
	* ( at least ) doubling the GPU RAM usage		:Use only the resolutions you need, and keep resolutions below certain limits, especially Power-Of-Two limits.
			::An image with a width of 1024 will be placed in a 1024 texture
	* Under NVidia, ~~disable~~ for optimal performance:		::An image with a width of 1025 will be placed in a 2048 texture,
	** - anisotropic filtering		*( at least ) doubling the GPU RAM usage
	** - antialiasing		*Under NVidia, for optimal performance, disable the following:
	** - texture filtering		:Anisotropic filtering
			:Antialiasing
			:Texture filtering

	* Use 'Single GPU Performance Mode' in combination with a Matrox to split the video output.		* Use 'Single GPU Performance Mode' in combination with a Matrox to split the video output.

Behrooz at 10:33, 5 February 2020

2020-02-05T10:33:03Z

← Older revision		Revision as of 10:33, 5 February 2020
Line 18:		Line 18:
	*Open several streams at the same time until the CPU usage does not grow anymore. You've reached the maximum throughput of your disk. <br>		*Open several streams at the same time until the CPU usage does not grow anymore. You've reached the maximum throughput of your disk. <br>

	~~Solutions~~		Solution
	*For best disk performance, use a disk array. Use fast disks ( >= 10k rpm ).		*For best disk performance, use a disk array. Use fast disks ( >= 10k rpm ).
	*Use M.2 SSDs, use SSDs in arrays, they perform up to more than 500MB/s.		*Use M.2 SSDs, use SSDs in arrays, they perform up to more than 500MB/s.
Line 37:		Line 37:
	:*Open eg. a movie >= 4k ( with demanding content! ) and if it does not play in realtime AND you see a CPU use of ca. 25% on a 4-core system, you are CPU limited. <br>		:*Open eg. a movie >= 4k ( with demanding content! ) and if it does not play in realtime AND you see a CPU use of ca. 25% on a 4-core system, you are CPU limited. <br>
	:*Or play a movie ( ideally with sound ) and while it is playing, constantly open and close other clips. If the first movie starts jittering, you are CPU limited. <br>		:*Or play a movie ( ideally with sound ) and while it is playing, constantly open and close other clips. If the first movie starts jittering, you are CPU limited. <br>
	~~Solutions~~		Solution
	*The solution is to get a faster CPU ( where MHz are in this case more important than the number of cores ) or - most of the times easier - reduce server load, eg. split videos, combine outputs, reduce resolutions, etc.		*The solution is to get a faster CPU ( where MHz are in this case more important than the number of cores ) or - most of the times easier - reduce server load, eg. split videos, combine outputs, reduce resolutions, etc.

	=== GPU ===		=== GPU ===

	* MXW renders 100% on the GPU, no pixel ~~colour~~ is touched on the CPU side.		MXW renders 100% on the GPU, no pixel color is touched on the CPU side. <br>
	* The performance of GPUs varies widely, some GPUs have 4 pixels processors, some have ~~1000~~. If you have a recent model ( bought since ~~2009~~ ), you should not experience ~~too~~ performance problems on GPU side. But there are important limits, most ~~noteably~~ GPU RAM~~, this~~ means, the dedicated GPU RAM built onto the graphics device. If you run out of GPU RAM, there will be a severe performance loss. A lot of GPU RAM is used when there are		The performance of GPUs varies widely, some GPUs have 4 pixels processors, some have 1000s. If you have a recent model ( bought since 2015 ), you should not experience much performance problems on the GPU side. But there are important limits, most notably GPU RAM. This means, the dedicated GPU RAM built onto the graphics device. If you run out of GPU RAM, there will be a severe performance loss. <br>
			A lot of GPU RAM is used when there are:
			*Many images open,
			*images with very large sizes open,
			*many effects used,
			*extreme large output sizes.

	** - many images open		Am i GPU limited? <br>
	** - images with very large sizes open
	** - many effects used
	** - extreme large output sizes

	''Am i GPU limited?''
	* GPU limitation is reached, when it takes very long time to open eg. dialog boxes.		* GPU limitation is reached, when it takes very long time to open eg. dialog boxes.
	* Reduce the output size. Use less effects. Delete some images, delete some videos. If the performance rises, you are GPU and/or GPU RAM limited.		* Reduce the output size. Use less effects. Delete some images, delete some videos. If the performance rises, you are GPU and/or GPU RAM limited.

Behrooz at 10:17, 5 February 2020

2020-02-05T10:17:54Z

← Older revision		Revision as of 10:17, 5 February 2020
Line 33:		Line 33:

	Test <br>		Test <br>
	*Open the task manager.		:Open the task manager.
	:*On modern multicore systems, the real situation hides behind the figures: if you cannot parallelize a task, and a single core cannot handle the problem in realtime, you are CPU limited. <br>		:*On modern multicore systems, the real situation hides behind the figures: if you cannot parallelize a task, and a single core cannot handle the problem in realtime, you are CPU limited. <br>
	:*Open eg. a movie >= 4k ( with demanding content! ) and if it does not play in realtime AND you see a CPU use of ca. 25% on a 4-core system, you are CPU limited. <br>		:*Open eg. a movie >= 4k ( with demanding content! ) and if it does not play in realtime AND you see a CPU use of ca. 25% on a 4-core system, you are CPU limited. <br>