Hello, I need to create a web-gui for an existing Lisp application and looked around for existing web-frameworks. I liked the ideas behind weblocks, but never had the occasion until now to use it for something real. I downloaded it today and after some twaeks to make it run (on LW 5.1.2/ Windows/32-bit), I stumbled upon the performance of the demo application, even after minutes of clicking around, to avoid inefficiencies, coming from compiling or preloading some data on startup of the demo :
1. to switch between the "Employees" and "Companies" views takes on my computer about 14 seconds; 2. to switch back to the "Employess" view takes the same 14 seconds; 3. to sort the emloyees by whatever takes about 4 seconds; 4. when i delete one of the employees, it takes about 5 seconds to get the confirmation box and another 5 to update the data in the browser; 5. clicking on "select all" above the employess' table, which has 2 rows at that moment takes about 4 seconds; 6.clicking on the "refresh"-button in firefox 3.0.7 after that, produces a request to the server, which takes 18 seconds to complete. In every single case - the CPU is going between 50% (for the most) and up to 99% for the rest time of the processing of the client request. The processing time is eaten in the weblocks-server running in the LispWorks-image. The computer I use is a dual-core 2.4ghz with 3gb ram and WinXP. I'm really new to weblocks, so my question: is this cpu/time-burning something inherent to the current architecture of weblocks, if yes - is there a hope to have it better? Or is it connected with the demo itself? Or can it be connected with the fact, that i didn't install it using clbuild, but loading all the newest versions of weblocks and the required libraries manually? With best regards Plamen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "weblocks" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/weblocks?hl=en -~----------~----~----~----~------~----~------~--~---
