Reply to thread

Message

<blockquote data-quote="Trident" data-source="post: 1063108" data-attributes="member: 99014">Increasing the number of concurrent processes in programming is usually done with the sole intention to prevent crash and disfunction of critical tasks, in the event of an error. Otherwise said, it is for stability purposes. It also prevents currently performed tasks from slowing down others which may be urgent.Some vendors may have put more attention in handling exceptions and multi-core optimisation.Consuming more random access memory may or may not optimise performance, it depends on programmers. If Bitdefender has decided to keep definitions and other code loaded in memory, they’ve deemed this will decrease disk reads and will speed everything up.In any case, there is no right or wrong approach as programming, albeit governed by some guidelines, is not strictly set in stone. Bitdefender’s multitude of processes and high memory consumption is just one way of doing things.</blockquote>

[QUOTE="Trident, post: 1063108, member: 99014"] Increasing the number of concurrent processes in programming is usually done with the sole intention to prevent crash and disfunction of critical tasks, in the event of an error. Otherwise said, it is for stability purposes. It also prevents currently performed tasks from slowing down others which may be urgent. Some vendors may have put more attention in handling exceptions and multi-core optimisation. Consuming more random access memory may or may not optimise performance, it depends on programmers. If Bitdefender has decided to keep definitions and other code loaded in memory, they’ve deemed this will decrease disk reads and will speed everything up. In any case, there is no right or wrong approach as programming, albeit governed by some guidelines, is not strictly set in stone. Bitdefender’s multitude of processes and high memory consumption is just one way of doing things. [/QUOTE]

Verification