Reply to thread

Message

<blockquote data-quote="Sebastiii" data-source="post: 1105803" data-attributes="member: 60104">Hi <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />Good Job m8 and usefull critical information too :1) Plugins shouldn't do any long lasting work (more than few ms) in plugin startup2) Plugins shouldn't do any processing in MP Main thread at all. All work should be dispatched to a worker thread(s). Reason for this is that if you have 10 plugins that are all doing 1 ms work in the main trhead you are already eating 50% of the frame rendering time on 50fps screen updates.3) Any network or local HD access is always more than 1 ms so they need worker thread(s) to be used even if plugin startup shouldn't do such.Thanks Guys <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /></blockquote>

[QUOTE="Sebastiii, post: 1105803, member: 60104"] Hi :) Good Job m8 and usefull critical information too : 1) Plugins shouldn't do any long lasting work (more than few ms) in plugin startup 2) Plugins shouldn't do any processing in MP Main thread at all. All work should be dispatched to a worker thread(s). Reason for this is that if you have 10 plugins that are all doing 1 ms work in the main trhead you are already eating 50% of the frame rendering time on 50fps screen updates. 3) Any network or local HD access is always more than 1 ms so they need worker thread(s) to be used even if plugin startup shouldn't do such. Thanks Guys :) [/QUOTE]

Verification