From 760bebd969c16bde041bb7fe839ea82d2866f674 Mon Sep 17 00:00:00 2001 From: Thomas Forgione Date: Mon, 7 Oct 2019 10:43:02 +0200 Subject: [PATCH] Fix sentence --- src/conclusion/future-work.tex | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/conclusion/future-work.tex b/src/conclusion/future-work.tex index 474cb86..75dd822 100644 --- a/src/conclusion/future-work.tex +++ b/src/conclusion/future-work.tex @@ -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.