Adam-
I'm beta testing a new database with a split FE/BE. It works fine with local users - data intense forms take 3-6 sec to load. With remote users, those same forms take 1-3 min to load, if at all. The BE is 104mb. The FE is ~35mb. What are some ideas to fix this?
The one idea I've come up with is, upon login, to upload at least the key data to FE tables. By key data, I'm talking about revenue, going back 3 years, which is then grouped and summarized in different ways. This data is updated only monthly, and isn't changed by users, so doesn't matter if the data is static. I could even compare a date field to see if there's new data before updating. It's this revenue data where there are calculations and summaries. I think client info could still reside on the BE, since they would only be pulling one record at a time, but I could test that, then copy that over too if necessary.
All the remote users will be read only - viewing data, downloading reports, exporting to Excel. Anyone making changes to client info is local. Revenue data will be uploaded to the back end.
The BE is being moved to a SQL server, but that may take a few weeks to set up. Is that going to make a difference, or will I still have the issue of sending large chunks of data through a smaller pipe?
Thanks
Adam
Posted by: John Viescas <johnv@msn.com>
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (2) |
Tidak ada komentar:
Posting Komentar