aindreas/fyp
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[report]: Mention useMemo

Browse Source
This commit is contained in:
Aindréas Ó hAodha
2025-04-03 03:25:04 +01:00
parent 46f5973ee5
commit e31bcae676
3 changed files with 12 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
report/references.bib
View File

@ -524,3 +524,12 @@
url = "https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/read-write-operations.html", url = "https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/read-write-operations.html",
urldate = "2025-04-02" urldate = "2025-04-02"
} }
@online{usememo,
author = {Meta Open Source},
title = {useMemo},
organisation = {React Documentation},
year = {2023},
url = {https://react.dev/reference/react/useMemo},
urldatel = {2025-04-03},
}

BIN
report/report.pdf
View File

Binary file not shown.

4
report/report.tex
View File

@ -1106,7 +1106,9 @@ long enough that it won't be triggered until the user pauses typing, but short e
\\\\ \\\\
However, if very large amounts of data are being displayed, such as in the event that the user has selected all data sources, the search can take a noticeable amount of time and make the UI sluggish \& unresponsive as the search is executed. However, if very large amounts of data are being displayed, such as in the event that the user has selected all data sources, the search can take a noticeable amount of time and make the UI sluggish \& unresponsive as the search is executed.
To address this, if the number of items being displayed is so high that it will induce noticeably slow loading times, the debounce time is increased to 400 milliseconds to be more careful in avoiding unnecessary computations, and the loading overlay is displayed as the filtering is performed to prevent the user from being exposed to a sub-optimally performant UI. To address this, if the number of items being displayed is so high that it will induce noticeably slow loading times, the debounce time is increased to 400 milliseconds to be more careful in avoiding unnecessary computations, and the loading overlay is displayed as the filtering is performed to prevent the user from being exposed to a sub-optimally performant UI.
\\\\
The search function makes use of the \mintinline{js}{useMemo}\supercite{usememo} React hook to cache the results of filtering the markers based off the search text, and making it so that it will only be re-calculated if the search term changes or if the markers change.
Without \mintinline{js}{useMemo}, every re-render of the page would cause the filter function to run even if nothing had changed, which would be a huge waste of computational resources.
\subsubsection{Map} \subsubsection{Map}
The map component itself is the presentational component in which all of the mapping \& plotting functionality is performed, implemented using the Leaflet\supercite{leaflet} mapping libraries and map tiles from OpenStreetMap\supercite{osm}. The map component itself is the presentational component in which all of the mapping \& plotting functionality is performed, implemented using the Leaflet\supercite{leaflet} mapping libraries and map tiles from OpenStreetMap\supercite{osm}.
It receives the markers to be displayed, a Boolean determining whether clustering is enabled, and the geolocation of the user, if available. It receives the markers to be displayed, a Boolean determining whether clustering is enabled, and the geolocation of the user, if available.