git.blender.org/blender.git - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author
2019-04-17	ClangFormat: apply to source, most of intern	Campbell Barton
	Apply clang format as proposed in T53211. For details on usage and instructions for migrating branches without conflicts, see: https://wiki.blender.org/wiki/Tools/ClangFormat
2018-11-30	Fix T58183: crash with CPU + GPU rendering after profiling changes.	Brecht Van Lommel
	Multi-device was not passing along profiler to the CPU.
2018-11-29	Cycles: Add sample-based runtime profiler that measures time spent in ↵	Lukas Stockner
	various parts of the CPU kernel This commit adds a sample-based profiler that runs during CPU rendering and collects statistics on time spent in different parts of the kernel (ray intersection, shader evaluation etc.) as well as time spent per material and object. The results are currently not exposed in the user interface or per Python yet, to see the stats on the console pass the "--cycles-print-stats" argument to Cycles (e.g. "./blender -- --cycles-print-stats"). Unfortunately, there is no clear way to extend this functionality to CUDA or OpenCL, so it is CPU-only for now. Reviewers: brecht, sergey, swerner Reviewed By: brecht, swerner Differential Revision: https://developer.blender.org/D3892
2018-11-09	Cycles: Cleanup, spacing after preprocessor	Sergey Sharybin
	It is supposed to be two spaces before comment stating which if else/endif statements corresponds to. Was mainly violated in the header guards.
2017-08-23	Fix implementation of atomic update max and move to a central location	Mai Lavelle
	While unlikely to have had any serious effects because of limited use, the previous implementation was not actually atomic due to a data race and incorrectly coded CAS loop. We also had duplicates of this code in a few places, it's now been moved to a single location with all other atomic operations.
2017-03-29	Cycles: Make all #include statements relative to cycles source directory	Sergey Sharybin
	The idea is to make include statements more explicit and obvious where the file is coming from, additionally reducing chance of wrong header being picked up. For example, it was not obvious whether bvh.h was refferring to builder or traversal, whenter node.h is a generic graph node or a shader node and cases like that. Surely this might look obvious for the active developers, but after some time of not touching the code it becomes less obvious where file is coming from. This was briefly mentioned in T50824 and seems @brecht is fine with such explicitness, but need to agree with all active developers before committing this. Please note that this patch is lacking changes related on GPU/OpenCL support. This will be solved if/when we all agree this is a good idea to move forward. Reviewers: brecht, lukasstockner97, maiself, nirved, dingto, juicyfruit, swerner Reviewed By: lukasstockner97, maiself, nirved, dingto Subscribers: brecht Differential Revision: https://developer.blender.org/D2586
2016-11-15	Atomics: Make naming more obvious about which value is being returned	Sergey Sharybin

2016-10-24	Cycles: Fix static initialization order fiasco	Sergey Sharybin
	Initialization order of global stats and node types was not strictly defined and it was possible to have node types initialized first and stats after that. This will zero out memory which was allocated from the statistics causing assert failure when de-initializing node types.
2014-12-25	Cleanup: Fix Cycles Apache header.	Thomas Dinges
	This was already mixed a bit, but the dot belongs there.
2014-12-02	Cycles: Use lock in the memory statistics	Sergey Sharybin
	CPU rendering is allowed to allocate memory from multiple threads, which means statistics need to be avare of this.
2014-09-04	Fix wrong track of the memory when doing device vector resize before freeing it	Sergey Sharybin
	This is rather legit case which happens i.e. when having persistent images enabled and session is updating the lookup tables. Now device_memory keeps track of amount of memory being allocated on the device, which makes freeing using the proper allocated size, not the CPU side buffer size.
2013-08-18	Cycles: relicense GNU GPL source code to Apache version 2.0.	Brecht Van Lommel
	More information in this post: http://code.blender.org/ Thanks to all contributes for giving their permission!
2012-11-09	Cycles: no need in spin lock in memory statistics	Sergey Sharybin
	This functions are called from device code which is guaranteed not to be called simultaneously from different threads.
2012-11-05	Cycles: memory usage report	Sergey Sharybin
	This commit adds memory usage information while rendering. It reports memory used by device, meaning: - For CPU it'll report real memory consumption - For GPU rendering it'll report GPU memory consumption, but it'll also mean the same memory is used from host side. This information displays information about memory requested by Cycles, not memory really allocated on a device. Real memory usage might be higher because of memory fragmentation or optimistic memory allocator. There's really nothing we can do against this. Also in contrast with blender internal's render cycles memory usage does not include memory used by scene, only memory needed by cycles itself will be displayed. So don't freak out if memory usage reported by cycles would be much lower than blender internal's. This commit also adds RenderEngine.update_memory_stats callback which is used to tell memory consumption from external engine to blender. This information is used to generate information line after rendering is finished.