Why does turning the visibility of a figure to "off" slow things down?

Question

Michael Mancinelli 2015-11-19

0
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/256523-why-does-turning-the-visibility-of-a-figure-to-off-slow-things-down

评论： Mike Garrity 2015-11-23

I have an application where turning the visibility of the figure off actually quadruples the run time of my program. I do a lot of axis and lighting manipulations between grabbing the screen.

Here is brief example that leads to a roughly 10% increase in time:

%%->> Visible ON<<-
tic
h = figure('Visible', 'On');
surf(peaks);
light;
axis([10 40 10 40 -5 5]);
h.Color = 'r';
view(45,45);
data = getframe();
toc
%%->>Visible OFF<<-
tic
h = figure('Visible', 'Off');
surf(peaks);
light;
axis([10 40 10 40 -5 5]);
h.Color = 'r';
view(45,45);
data = getframe();
toc

Basically, I would love an explanation as to why MATLAB acts any differently when the figure is not displayed!

0 个评论
显示 -2更早的评论隐藏 -2更早的评论

请先登录，再进行评论。

请先登录，再回答此问题。

Answer 1

Mike Garrity 2015-11-19

0
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/256523-why-does-turning-the-visibility-of-a-figure-to-off-slow-things-down#answer_200531

They actually don't do the same thing at all.

In the Visible='on' case, the pixels are already sitting in the framebuffer on the graphics card. The getframe function just fetches them.

In the Visible='off' case, there is no framebuffer and the graphics haven't already been drawn. So the getframe command basically starts a print job. Printing is nearly as tightly optimized as on screen rendering because it supports lots of additional features that you're not using here. For one thing, it needs to allocate a number of resources which are basically free when you're drawing into the framebuffer.

2 个评论
显示无隐藏无

Walter Roberson 2015-11-19

Mike, is that "is nearly" or "is not nearly" ? The "is nearly" would imply that the timing should be very close, which the rest of your discussion seems to argue otherwise.

Mike Garrity 2015-11-23