Suspicious PhysicalFileProvider Memory Usage

Question

Im yet to fully test, but i would like to know how the "Feature" Physical File Provider filemanager code will perform with a directory of several thousand nested files and an estimated 100GB of data. Early tests indicate it is unable to process and is tying up large amounts of server memory... Would make sense, since it is using DirectoryInfo... However, this should release after the reult is returned to the client....

running visual studio diagnostic tools shows a continuous climb in memory every time i navigate to the same folder, and memory is not released when navigating away from the file manager.

I also note that the git asp.net core fileprovider code is perhaps 2 years old.... Is it the same as the Blazor "FileManager-Feature" code scaffold template?

Indhumathy Loganathan · Answer

Hi Daniel,Greetings
from Syncfusion support.We
understand that you are validating our File Manager component with large data
in the Physical File Service provider. We need some additional time to validate
this query and will check the File Manager memory usage with 100 GB of data. We
will update you with further details on or before May 23, 2022. We appreciate
your patience.Regards,Indhumathy
L

Indhumathy Loganathan · Answer

Hi Daniel,Thanks for your patience.To validate
the reported issue, we have prepared the Blazor File Manager component with the
Physical File Service provider in the latest package version and added 100 GB
of data. We were unable to identify the mentioned issue while analyzing the
sample, and there is no memory leak in the File Manager
component and it is removed from the memory during page navigation. We have attached the screenshots for your reference.Empty razor page
to File Manager component razor page.File Manager component
razor page to Empty razor page.We
understand that you are facing some memory usage at your end while using the
File Manager component. But in order to reproduce it, we need some more
additional details. Please share with us the exact steps you have followed to
identify the memory climbing issue. the package version used in your sample.
These details would help us assist you promptly.Regards,Indhumathy
L

Daniel Reibelt · Answer

Thanks, i will get back to you as soon as i have time to test this.

Indhumathy Loganathan · Answer

Hi Daniel,Thanks for
the update. We will wait to hear from you.Regards,Indhumathy
L