Static vs Object Method Performance Considerations

2 次查看（过去 30 天）
Abel
Abel 2012-10-18
Are there any performance considerations regarding Static vs. object methods in MATLAB OOP?
  6 个评论
显示 4更早的评论
Daniel Shub
Daniel Shub 2012-10-19
@Matt J, It used to be that vectorization was the be all and end all of MATLAB since loops were slow. For over 10 years now MATLAB has had a JIT accelerator which often makes loops the same speed (and sometimes faster) than vectorized code.
Matt J
Matt J 2012-10-19
编辑：Matt J 2012-10-19
@Abel - the problem with your test, though, is that even though you've declared your data constant, you have to execute the command "test.f" to access the data. This is something like calling an mfile function, I'd assume, and there is overhead associated with that. When the data you're processing is small in comparison to the overhead needed to access it, you get misleading results. I believe you even encountered the same issue here
http://www.mathworks.com/matlabcentral/newsreader/view_thread/323890
@Daniel - the JIT has its benefits, bit it hasn't leveled the playing field completely. It will always be true, I think, that in a loop, if a function is given too small a chunk of data to process, the overhead from just launching the function (repeatedly) will kill you.

请先登录，再进行评论。

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

回答（1 个）

Daniel Shub
Daniel Shub 2012-10-19
Dave Foti who manages the OOP group at TMW has a post on Loren's blog that touches on some of these issues.
For your example I am not sure how smart the MATLAB JIT accelartor is and when things get reallocated and refreshed. It seems to me that once getc1 and getc2 are loaded into memory (remember MATLAB parses and loads functions into memory), that they are identical.

类别

在 Help Center 和 File Exchange 中查找有关 Software Development Tools 的更多信息

标签

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by