Is setappdata and getappdata a good replacement of global variables?
6 views (last 30 days)
Akhilesh Thakur on 12 Dec 2017
I know appdata is generally a wrapper code of set and get. Like set(0,'ApplicationData',t1); and get(0,'ApplicationData');. I have large set of codes that uses global variables and I was wondering whether using appdata would increase my speed of computation. I know in MATLAB the order of performance is inline > file-pass = nest-pass = sub-pass > nest-share > sub-global > file-global. I tried maintaining to order the code to pass variables from functions, but sometimes its tedious to do that. Is anyone really familiar with Application Data of MATLAB, I am really interested to know more about that as right know I have started using that and it looks good for now.
Walter Roberson on 12 Dec 2017
getappdata() requires a function call, as does set(). That is always going to be slower than a non-object variable access, even a global access. (For objects, there are different cases, one of which would be like accessing a struct but the others would involve function calls.)
Note that every call to guidata() involves climbing the ancestry of the given object to find the figure and then doing a getappdata() on it. GUIDE does this automatically for every callback, in order to supply the handles struture to the callback.
When you have something like the handles struct, then every call to getappdata() takes a copy of the struct. This suggests that it is often not a good idea to store large data in the handles struct; this would not be a problem if you were going to use the large data in every callback but most callbacks use only a small number of handle fields. Thus, if you have large data that you would normally consider storing in the handles struct, it is usually better to use setappdata() / getappdata() for it, so that you can take the hit of copying in the data only when you specifically need it.
For your purposes, you should probably be considering either using shared variables or else using handle objects: handle objects act like pointers, not needing to copy in the contents of the object.