Page 1 of 3 123 LastLast
Results 1 to 10 of 21

Thread: Page file usage

  1. #1
    Join Date
    Dec 2017
    Posts
    117

    Default Page file usage

    I'm working on a file that doesn't seem excessively big--about 4 million polygons in render meshes--and have been seeing out-of-memory issues. I look at my basic memory usage (32 GB physical RAM) and it's not even close to filled up, but then I look closer and oh it's the "Commit" size, so for example right now my total Windows RAM use is 14.6 GB but the total commit is 42.1, with 24.2 of that from Rhino. Why is it not making use of more of my physical RAM? Is it even really using that page file space?

  2. #2
    Join Date
    Dec 2017
    Location
    Melbourne, Australia
    Posts
    310

    Default

    What is actually reporting out of memory, Iray somehow or your system in general? Note that it's GPU memory that is likely the issue in Iray's case not system memory. Do you have any screenshots of the error.

  3. #3
    Join Date
    Dec 2017
    Posts
    117

    Default

    I'll see if I can reproduce it, of course now I won't be able to. The error message is Rhino's standard memory allocation failed, emergency file saved message. Rendering the scene does not seem to be taxing video memory(4 X 11GB 1080ti.)

  4. #4
    Join Date
    Dec 2017
    Posts
    117

    Default

    So here is a screenshot of the memory error and the Task Manager memory info. This is weird, this error might be some sort of bug, this happens reliably on this file now upon trying to open the NamedView panel, unless I turn off the Thumbnails with the file closed.

    Click image for larger version. 

Name:	out of memory error.jpg 
Views:	11 
Size:	566.3 KB 
ID:	10687

  5. #5
    Join Date
    Dec 2017
    Location
    Melbourne, Australia
    Posts
    310

    Default

    Is there anything useful in your Iray logs? Do you have instancing turned on, if so you might try with that turned of.

  6. #6
    Join Date
    Dec 2017
    Posts
    117

    Default

    Instancing is off, no sign of anything in the log file.

  7. #7
    Join Date
    Dec 2017
    Location
    Melbourne, Australia
    Posts
    310

    Default

    It's pretty hard to say. Given the scene is not especially huge it may be one troublesome object that is causing issues rather than the overall complexity. My usual way to track those down is to save a new file, then remove half the objects and see if it still occurs, if not then the other half, then half that half and so on until its narrowed down. Annoying but if it is a particular object it will quickly find it.

  8. #8
    Join Date
    Dec 2017
    Posts
    117

    Default

    So this is the log file, it hasn't crashed, but it's still using an awful lot of memory.

    1.0 IRAY rend info : Updating geometry.
    1.0 IRAY rend info : Using OptiX Prime ray tracing (5.0.1).
    1.0 IRAY rend info : Importing scene graph.
    1.0 IRAY rend info : Importing geometry for motion time 0
    1.0 IRAY rend info : Geometry import (1 object with 3594k triangles, 1 instance yielding 3594k triangles) took 1.294483
    1.0 IRAY rend info : Updating materials.
    1.0 MATCNV rend info : Material instance 'irayMaterial_36' uses MDL JIT compilation.
    1.0 MATCNV rend info : Material instance 'irayMaterial_72' uses MDL JIT compilation.
    1.0 MATCNV rend info : Material instance 'irayMaterial_35' uses MDL JIT compilation.
    1.0 MATCNV rend info : found 64 textures, 6 lambdas (2 unique)
    1.0 IRAY rend info : Emitter geometry import (33 light sources with 1664 triangles, 1 instance) took 0.00s
    1.0 IRAY rend info : Updating environment.
    1.0 IRAY rend info : Updating backplate.
    1.0 IRAY rend info : Updating lens.
    1.0 IRAY rend info : Updating lights.
    1.0 IRAY rend info : Updating object flags.
    1.0 IRAY rend info : Updating caustic portals.
    1.0 IRAY rend info : Updating decals.
    1.0 IRAY rend info : Allocating 1-layer frame buffer
    1.0 IRAY rend info : Using interactive scheduling, architectural sampler unavailable, caustic sampler enabled
    1.0 IRAY rend info : Initializing local rendering.
    1.0 IRAY rend info : Rendering with 4 device(s):
    1.0 IRAY rend info : CUDA device 3 (GeForce GTX 1080 Ti)
    1.0 IRAY rend info : CUDA device 0 (GeForce GTX 1080 Ti)
    1.0 IRAY rend info : CUDA device 1 (GeForce GTX 1080 Ti)
    1.0 IRAY rend info : CUDA device 2 (GeForce GTX 1080 Ti)
    1.0 IRAY rend info : Rendering...
    1.12 IRAY rend progr: CUDA device 0 (GeForce GTX 1080 Ti): Processing scene...
    1.11 IRAY rend progr: CUDA device 3 (GeForce GTX 1080 Ti): Processing scene...
    1.13 IRAY rend progr: CUDA device 1 (GeForce GTX 1080 Ti): Processing scene...
    1.3 IRAY rend progr: CUDA device 2 (GeForce GTX 1080 Ti): Processing scene...
    1.10 IRAY rend stat : Geometry memory consumption: 144.703 MiB (device 1), 0 B (host)
    1.8 IRAY rend stat : Geometry memory consumption: 144.703 MiB (device 0), 0 B (host)
    1.9 IRAY rend stat : Geometry memory consumption: 144.703 MiB (device 3), 0 B (host)
    1.2 IRAY rend stat : Geometry memory consumption: 144.703 MiB (device 2), 0 B (host)
    1.9 IRAY rend stat : Texture memory consumption: 244.321 MiB for 30 bitmaps (device 3)
    1.9 IRAY rend info : Importing lights for motion time 0
    1.9 IRAY rend info : Initializing light hierarchy.
    1.2 IRAY rend stat : Texture memory consumption: 244.321 MiB for 30 bitmaps (device 2)
    1.9 IRAY rend info : Light hierarchy initialization took 0.02s
    1.9 IRAY rend stat : Lights memory consumption: 301.082 KiB (device 3)
    1.2 IRAY rend stat : Lights memory consumption: 301.082 KiB (device 2)
    1.10 IRAY rend stat : Texture memory consumption: 244.321 MiB for 30 bitmaps (device 1)
    1.8 IRAY rend stat : Texture memory consumption: 244.321 MiB for 30 bitmaps (device 0)
    1.10 IRAY rend stat : Lights memory consumption: 301.082 KiB (device 1)
    1.8 IRAY rend stat : Lights memory consumption: 301.082 KiB (device 0)
    1.9 IRAY rend stat : Material measurement memory consumption: 0 B (GPU)
    1.9 IRAY rend stat : PTX code (4.25 KiB) for sm61 generated in 0.0121s
    1.9 IRAY rend stat : Materials memory consumption: 349.719 KiB (GPU)
    1.8 IRAY rend stat : PTX code (4.25 KiB) for sm61 generated in 1.7e-06s
    1.2 IRAY rend stat : PTX code (4.25 KiB) for sm61 generated in 6e-07s
    1.10 IRAY rend stat : PTX code (4.25 KiB) for sm61 generated in 5e-07s
    1.9 IRAY rend info : JIT-linking wavefront kernel in 0.076s
    1.2 IRAY rend info : JIT-linking wavefront kernel in 0.132s
    1.8 IRAY rend info : JIT-linking wavefront kernel in 0.124s
    1.9 IRAY rend info : JIT-linking mega kernel in 0.096s
    1.11 IRAY rend info : CUDA device 3 (GeForce GTX 1080 Ti): Scene processed in 3.193s
    1.9 IRAY rend info : CUDA device 3 (GeForce GTX 1080 Ti): Allocated 11.8058 MiB for frame buffer
    1.10 IRAY rend info : JIT-linking wavefront kernel in 0.104s
    1.2 IRAY rend info : JIT-linking mega kernel in 0.053s
    1.3 IRAY rend info : CUDA device 2 (GeForce GTX 1080 Ti): Scene processed in 3.228s
    1.8 IRAY rend info : JIT-linking mega kernel in 0.055s
    1.12 IRAY rend info : CUDA device 0 (GeForce GTX 1080 Ti): Scene processed in 3.237s
    1.9 IRAY rend info : CUDA device 2 (GeForce GTX 1080 Ti): Allocated 11.8058 MiB for frame buffer
    1.8 IRAY rend info : CUDA device 0 (GeForce GTX 1080 Ti): Allocated 11.8058 MiB for frame buffer
    1.10 IRAY rend info : JIT-linking mega kernel in 0.035s
    1.13 IRAY rend info : CUDA device 1 (GeForce GTX 1080 Ti): Scene processed in 3.248s
    1.11 IRAY rend info : CUDA device 3 (GeForce GTX 1080 Ti): Allocated 1.6875 GiB of work space (2048k active samples in 0.067s)
    1.11 IRAY rend info : CUDA device 3 (GeForce GTX 1080 Ti): Used for display, optimizing for interactive usage (performance could be sacrificed)
    1.8 IRAY rend info : CUDA device 1 (GeForce GTX 1080 Ti): Allocated 11.8058 MiB for frame buffer
    1.3 IRAY rend info : CUDA device 2 (GeForce GTX 1080 Ti): Allocated 1.6875 GiB of work space (2048k active samples in 0.061s)
    1.12 IRAY rend info : CUDA device 0 (GeForce GTX 1080 Ti): Allocated 1.6875 GiB of work space (2048k active samples in 0.063s)
    1.13 IRAY rend info : CUDA device 1 (GeForce GTX 1080 Ti): Allocated 1.6875 GiB of work space (2048k active samples in 0.063s)
    1.0 IRAY rend info : Received update to 00001 iterations after 3.674s.
    1.0 IRAY rend info : Rendering...
    1.0 IRAY rend info : Received update to 00002 iterations after 3.897s.
    1.0 IRAY rend info : Received update to 00003 iterations after 4.087s.
    1.0 IRAY rend info : Received update to 00004 iterations after 4.286s.
    1.0 IRAY rend info : Received update to 00005 iterations after 4.470s.
    1.0 IRAY rend info : Received update to 00006 iterations after 4.663s.
    1.0 IRAY rend info : Received update to 00007 iterations after 4.849s.
    1.0 IRAY rend info : Received update to 00008 iterations after 5.040s.
    1.0 IRAY rend info : Received update to 00009 iterations after 5.231s.
    1.0 IRAY rend info : Received update to 00010 iterations after 5.422s.
    1.0 IRAY rend info : Received update to 00011 iterations after 5.608s.
    1.0 IRAY rend info : Received update to 00012 iterations after 5.795s.
    1.0 IRAY rend info : Received update to 00013 iterations after 5.987s.
    1.0 IRAY rend info : Received update to 00014 iterations after 6.207s.
    1.0 IRAY rend info : Received update to 00015 iterations after 6.400s.
    1.0 IRAY rend info : Received update to 00016 iterations after 6.593s.
    1.0 IRAY rend info : Received update to 00017 iterations after 6.804s.
    1.0 IRAY rend info : Received update to 00018 iterations after 6.991s.
    1.0 IRAY rend info : Received update to 00019 iterations after 7.176s.
    1.0 IRAY rend info : Received update to 00020 iterations after 7.364s.
    1.8 IRAY rend info : CUDA device 1 (GeForce GTX 1080 Ti): Allocated 11.585 MiB for frame buffer
    1.9 IRAY rend info : CUDA device 0 (GeForce GTX 1080 Ti): Allocated 11.9464 MiB for frame buffer
    1.5 IRAY rend info : CUDA device 2 (GeForce GTX 1080 Ti): Allocated 12.0699 MiB for frame buffer
    1.23 IRAY rend info : CUDA device 3 (GeForce GTX 1080 Ti): Allocated 11.6217 MiB for frame buffer

  9. #9
    Join Date
    Dec 2017
    Location
    Melbourne, Australia
    Posts
    310

    Default

    That would seem to indicate it is something in the part being held in Rhino by the plugin rather than internally in the renderer. Note that the plugin does keep a lot of data in working memory so a restart of Rhino will often clear a lot of memory. Not sure if you are seeing this behaviour even in a totally fresh session.

  10. #10
    Join Date
    Dec 2017
    Posts
    117

    Default

    In a fresh Rhino session it's fine, until...some point, reopening the file seems to induce the crash, sometimes without iRay itself even doing anything beyond loading the textures. Plus it seems that once this happens restarting Rhino isn't enough to fix it, I need to reboot.
    Last edited by jcarruthers; 7th June, 2019 at 05:19.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •