Sorry for the title of the post, it might sound a bit over the top, but I just made a simple performance test using message-boxes with some interesting results:
I do like to use message boxes to store temporarily some data (into the right inlet) and then pass it on with a bang on the left inlet. but this method is not very performativ compared with using a textedit.
Check out this patch:
its very simple, banging with metro as fast as possible a long message though a chain of message boxes vs. a chain of textedit boxes.
Running this patch on a 4 year old macbook pro, the result are stunning:
the 8 messageboxes let max soar up to use 75% of my CPU, while the framerate drops to 110.
the 8 textedit boxes use only 10% with 220 fps.
I am surprised that 8 messageboxes in such a simple patch can use up so much system resources (Actually with only 4 messageboxes it uses the same 75% of the CPU, too, but the framerate is better: 220)
so it looks like this unpretentious little gray box is attached to some serious overhead processes in the background.
now I wonder if there are some people that can confirm this find.
and I would like to know where this performance penalty comes from, and what it means for using messageboxes in high preformance patches where high framerates are important.
for me it looks like as if I am going to use textedit from now on in order to have a temporary storage.