Why is Grunt faster than Gulp?

Question

Web development

Goodnight.
Actually, the question is in the subject. Two typical tasks are building js\less and minifying them. Grunt + Jit-Grunt collects them for the first time in 4-5 seconds, and then the count goes to 3-6 tenths of a second. You can save the file and immediately update the browser - as a rule, everything is already assembled! Gulp, on the other hand, rarely does it faster than 10 seconds each time, and you have to wait until it finally finishes.
Relevant for both Win XP and Win 8.1; for single-core, and for quad-core processors; for a "clean" system, and for the one that has been using it for a year now. Reading the gulp "speed" hype, the question creeps in, what am I doing wrong?) The installation is standard, npm install -g gulp > npm install (locally).

Answer 1

Gulp, in theory, should win due to the parallelization of tasks and by placing intermediate results in memory (without writing to a slow screw). Inside, behind plugins, both have the same less and uglify2. So, purely theoretically, with two consecutive tasks, in each of which there are no intermediate steps, the speed should be of the same order.
PS I myself noticed that sometimes Gulp takes an abnormally long time to start, but I don’t know what the reason is yet.