I am working on a project which will generate lot data file (per user) around 0.5mb to 1.0mb.
supervisor was concern about the generating the files on server will spend too much processing resources, like CPU, Memory etc.
so a suggestion are proposed: generate the files on client side and submit to server
in theory server just need to receive the data and save to disk.
but I am not sure if this a good idea, because its had proven that:
- Generate the file on server will much more faster than upload time (same file size are generated) on normal internet speed.
as I understanding IIS will keep the connection alive until all data are transmitted,
then instancelize requested object and pass in the data and execute, it mean to me:
- if the upload time too long, mean IIS are able to handle less concurrent request, because the connection pool are occupied
- IIS required almost same memory useage, because it need to keep the uploaded data in memory
- IIS memory pool might recircle if too many users uploading, because the memory pool reached the threshold
- procssing time and power might be less, because only IO operation?
I dont know IIS much, please do advice if I'm wrongly undertsand how IIS work
and also please do tell me the pro and con about this implementation if possible.
Thank you very much