diff options
author | Boris Kolpackov <boris@codesynthesis.com> | 2014-11-26 07:44:46 +0200 |
---|---|---|
committer | Boris Kolpackov <boris@codesynthesis.com> | 2014-11-26 07:44:46 +0200 |
commit | 9b3f696b9643572ad41acda698da2d969c9b264f (patch) | |
tree | 3d6f4f666df490d6171bf9ce093acfb239728edf /quality | |
parent | a1b82626d7577da44d7b25534666e76226fd7788 (diff) |
Add quality: move change callback out of image
Diffstat (limited to 'quality')
-rw-r--r-- | quality/list | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/quality/list b/quality/list index 2ef008a..b7f0e0f 100644 --- a/quality/list +++ b/quality/list @@ -1 +1,15 @@ - Inconsistent id() vs direct access use in generated code + +? Move change_callback out of image + + We incur a bit of overhead in case of a batch (e.g., ~80KB for + a batch size of 5000 on 64-bit) since we don't use this callback + in all but the first element. + + The idea is to move it to the object statements, however, there + are several places that need to access it that only got the image + (e.g., init(image)). Storing a pointer in the image doesn't make + sense since the struct itself is two pointers. + + So it is not clear this is worth the effort. See also a separate + paper with some more thoughts on this. |