It used to be that for a 32 bit Windows (ie XP) Gimp started slowly in certain versions. After Gimp 2.8.4 up to (I think) 2.8.12 there was a lot of loading/initializing at each start-up.
I have a WinXPsp3 Virtual Machine, never updated after 2.8.4 for that reason.
Running that command takes 12 seconds, but updated to the latest Gimp 2.8.16 takes 14 seconds and that could be me + stopwatch + error.
So, not much in it.
Going to linux, speed is a bit different, using my regular PClinuxOS 32 bit, in a terminal, the command takes about 3 seconds (including lots of warnings from other dubious plugins I have installed)
So, you might be OK in a linux server.
However, depending what you want to do, ImageMagick might be a better bet for a server.
A little better measuring

WinXP about 12 seconds
Attachment:
cli.jpg [ 43.44 KiB | Viewed 3363 times ]
and in linux, probably a second or two if I ever get round to cleaning up my Gimp profile.
[rich@localhost ~]$ cd temp
[rich@localhost temp]$ sh cli.sh
user 0m0.00s
sys 0m0.00s
(gimp-console-2.8:19713): GLib-GObject-WARNING **: g_object_set_valist: object class 'GeglConfig' has no property named 'cache-size'
***lots and lots of warnings deleted****
(gimp-console-2.8:19713): LibGimpBase-WARNING **: gimp-console-2.8: gimp_wire_read(): error
batch command executed successfully
user 0m4.99s
sys 0m1.03s
[rich@localhost temp]$