MATLAB Answers

better way to improve performance of my code

3 ビュー (過去 30 日間)
Salvatore Mazzarino
Salvatore Mazzarino 2012 年 10 月 14 日
I'm doing a simulation using for cycle. In this simulation I have a series of fprintf that print out information. To improve the performance of my simulation I created a custom fprintf
function custom_fprintf(debug,varargin)
%FPRINTF Summary of this function goes here
% Detailed explanation goes here
if debug ~= 0
builtin('fprintf', varargin{:});
When debug is setted to 1, fprintf prints out the arguments passed. The problem is that examinating my code with profiler I see that when for cycle is executed for 10e6, the simulation spend too many time in custom_fprintf function. Which could be the way to improve this situation?
  4 件のコメント
Nathaniel 2012 年 10 月 14 日
I understand what you're doing, although I think you're mixing 2 different patterns from compiled languages.
One pattern is that you link against either a debug library or a non-debug library, and the debug version of the code includes the print command while the non-debug version is essentially a NOOP, which gets optimized out.
The other pattern is that you have the preprocessor either compile in debug code or not based on the existence of a defined constant. In C, this would be:
#ifdef DEBUG
MATLAB is not a compiled language, so you can't build as much flexibility into your code without sacrificing some performance. That said, an if statement in which the condition is x~=0 is probably almost the fastest line of MATLAB code possible. Having your code littered with if debug~=0...end may not be the prettiest solution, but it can't possibly be any slower than calling a function which executes the same if statement.


回答 (2 件)

Oleg Komarov
Oleg Komarov 2012 年 10 月 14 日
which waits half a second, i.e. 0.5*1e7 = 5e6 = about 1388.89 hours.
  2 件のコメント
Salvatore Mazzarino
Salvatore Mazzarino 2012 年 10 月 14 日
I'm looking for a fast way to print info when debug is setted to 1 and not print info when debug is setted to 0


Nathaniel 2012 年 10 月 14 日
Using varargin is what's killing you. You can get avoid this by constructing the cell array in the calling code, rather than relying on whatever mechanism MATLAB is using.
Try this for your custom_fprintf function:
function custom_fprintf(DEBUG, args)
Then call it like this:
for n=1:1e6
custom_fprintf(DEBUG, {'this is the format string %d\n', n});
This construction should be just about as fast as putting the if statement in the calling code.


Community Treasure Hunt

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

Start Hunting!

Translated by