dash-3d-tmp
/
phd
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fix sentence

This commit is contained in:
Thomas Forgione 2019-10-07 10:43:02 +02:00
parent e7659e13a5
commit 760bebd969
No known key found for this signature in database
GPG Key ID: 203DAEA747F48F41
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
src/conclusion/future-work.tex
View File

@ -19,5 +19,5 @@ Performance has already been discussed in Chapter~\ref{d3}.
However, in this work, we never tried to remove data from the media engine when it is no longer useful.
This means that on a really large scene, performance is bound to become damaged due to the growing amount of data to render, and the saturation of memory.
For our system to be able to support such scenes, it needs to unload data.
The utility measures that we described in Section~\ref{d3:utility} seem to be a good candidate to determine what to unload.
We could watch the performance of our system by measuring variables such as memory used or framerate and use those values to discard data with low enough utility.
The utility measures that we described in Section~\ref{d3:utility} seem to be good candidates to determine what to unload.
We could estimate the performance of our system by measuring variables such as memory used or framerate and use those values to discard data with low enough utility.