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.

  • 相关阅读:
    小程序(四):模板
    小程序(三):授权登录
    小程序(二)
    小程序(一)
    从零开始学习微信小程序
    flex 弹性布局
    如何使用docker进行shadsocks环境开发配置
    eclipse 设置注释模板
    idea 2019.1.3最新注册码
    centos7安装rabbitmq简单方式
  • 原文地址:https://www.cnblogs.com/Jedimaster/p/1931040.html
Copyright © 2011-2022 走看看