zoukankan      html  css  js  c++  java
  • STOKES Birds of a Feather

    E5200 OC 2.9GHz, OpenMP 2 threads, rasterized 2 level noised density fields into a 512M volumn in 1150.62 seconds with paging system, used 130M memory, a deal between time and space.

    To stokes, I have to take care about multithreading, GPU and even network, paging system for DSO rendering etc.

    I decided to use block-based addresing mode not slice based, because of sparse accessing, compressing and paging. Why paging ? Assumed that we would raymarch an 8G density field file by a RenderMan DSO, we could not use too much memory but one slice in that file might up to 32MB, if we could only use up to 512M memory in DSO, we could just hold 16 slices in memory but we can cache much more blocks (a 64^3 density block only occupies 1M), that would be efficient when enabled adaptive sampling. At the same time, too large linear slice-based volumn can’t be loaded into GPU for previewing.

    What’s the most critical about a software ? Architecture. So, how to improve the architecture ? Spend more and more time about execution workflow. I still need a lot of time to re-factor the architecture, make it faster and more flexible.

  • 相关阅读:
    phpajax高级篇
    一天学会ajax (php环境)
    php生成静态文件的方法
    MongoDB查询文档
    MongoDB删除文档
    MongoDB索引管理
    MongoDB插入文档
    MongoDB排序记录
    MongoDB 更新文档
    mongoDB 固定集合(capped collection)
  • 原文地址:https://www.cnblogs.com/Jedimaster/p/1931040.html
Copyright © 2011-2022 走看看