- Fri Aug 26, 2016 6:41 am
#53838
OH, I'm no doubt running into other errors. I was using the recursion since the process of reading any one directory is essentially the same as reading any sub-directory, thus I called back on the same function to read the sub directory. I decided to go to the file output just because caching allows the server code itself to be more responsive rather than taking time out to do the same work over and over again.
I bugged one of the former C++ programmers at work and think I know how to pass the File handle around now, I just haven't had time to try it yet. I'm still curious to know why the jquery call never seems to complete though, but I've had to do some other things while stress testing the capability of these servers such as using a javascript lazy-loader and compressing the .js and .css files to get them to both load completely and do so in a timely fashion. (I was curious to see how long it would take on these little guys to load a full code suite including jquery, bootstrap, angularjs and sundry other scripts. Uncompressed it was taking up to a minute to load everything. Compressed I got them down to about 15-20 seconds. But concurrent connections seemed to fail occasionally, generally with the first file [bootstrap.css] not loading completely. It would freeze as the others started to load and then resume but not load correctly. I then tried combined them all into a single file, minified them and compressed them, and that I got it down to 10-12 seconds. But I still needed to load the bootstrap.css separate and it was still dropping chunks - so I went to using the lazy loader to make sure they loaded sequentially)
Now that my playing with top-heavy pages is done, I'm probably going to strip it all out and go back to basics using all native code and only the bare minimum functionality I need to get the job done. You can get lazy on big web servers with fast connections and load more than you need.
martinayotte wrote:I don't understand why you would need streaming and why are you talking about recursion ...
[/code]
OH, I'm no doubt running into other errors. I was using the recursion since the process of reading any one directory is essentially the same as reading any sub-directory, thus I called back on the same function to read the sub directory. I decided to go to the file output just because caching allows the server code itself to be more responsive rather than taking time out to do the same work over and over again.
I bugged one of the former C++ programmers at work and think I know how to pass the File handle around now, I just haven't had time to try it yet. I'm still curious to know why the jquery call never seems to complete though, but I've had to do some other things while stress testing the capability of these servers such as using a javascript lazy-loader and compressing the .js and .css files to get them to both load completely and do so in a timely fashion. (I was curious to see how long it would take on these little guys to load a full code suite including jquery, bootstrap, angularjs and sundry other scripts. Uncompressed it was taking up to a minute to load everything. Compressed I got them down to about 15-20 seconds. But concurrent connections seemed to fail occasionally, generally with the first file [bootstrap.css] not loading completely. It would freeze as the others started to load and then resume but not load correctly. I then tried combined them all into a single file, minified them and compressed them, and that I got it down to 10-12 seconds. But I still needed to load the bootstrap.css separate and it was still dropping chunks - so I went to using the lazy loader to make sure they loaded sequentially)
Now that my playing with top-heavy pages is done, I'm probably going to strip it all out and go back to basics using all native code and only the bare minimum functionality I need to get the job done. You can get lazy on big web servers with fast connections and load more than you need.
