About two and a half weeks ago my organization upgraded from Alpha Five version 8 to version 10.5. We've had plenty of bugs to work out of our application since that change, but have managed to fix or find work-arounds for most of them. However, this one's got me stumped:
One of the most important forms in our application displays names & addresses of individuals, then has 10 browses (on various tabs) displaying their orders/invoices, various types of donations, registrations in various events, etc. All of the browses are read only--data entry is done via dialogs or other forms. It's a rather large set and could have been somewhat better normalized, but it's been running well since version 5 the way it is. When we upgraded to version 10, we had to re-build each of the 10 embedded browses in order for the application to even run. Since then things have been running well--but only on our machines that run Windows 7.
On our XP machines, it takes literally 3 or 4 seconds to fetch a new customer in the form regardless of the current index (or lack thereof). When entering invoices (on a completely different form--we do use a browse for data entry there), it's likewise 3-6 seconds between hitting ctrl+enter on one line and when the next line is available to type in.
We currently have five win XP machines and three win 7 machines that use the database. All three Win 7 machines run the form beautifully. Four out of the five XP machines choke--and I didn't bother testing the fifth. I don't think it's a hardware related difference, but for the sake of comparison:
Computer #1--Way too slow:
Intel Core 2 Duo E8400 (3.0GHz)
3GB RAM
Gb ethernet
Network optimized database
Windows XP Pro 32-bit
Computer #2--Just great:
Intel Core 2 Duo E7500 (2.9GHz)
3GB RAM
Gb ethernet
Network optimized database
Windows 7 Pro 32-bit
Both computers are connected to the same Gb network switch. The real database files reside on another Core 2 Duo Win 7 machine on the same Gigabit switch. Currently we only have 3 users on the database at any given time, although it is usually open on five different workstations at once.
Ok, sorry for such a long post, but I figured I may as well give all the info up front. So here's the bottom line: Why such a performance hit under XP? Any suggestions on how to remedy the problem?
Thanks in advance!
~Jason
One of the most important forms in our application displays names & addresses of individuals, then has 10 browses (on various tabs) displaying their orders/invoices, various types of donations, registrations in various events, etc. All of the browses are read only--data entry is done via dialogs or other forms. It's a rather large set and could have been somewhat better normalized, but it's been running well since version 5 the way it is. When we upgraded to version 10, we had to re-build each of the 10 embedded browses in order for the application to even run. Since then things have been running well--but only on our machines that run Windows 7.
On our XP machines, it takes literally 3 or 4 seconds to fetch a new customer in the form regardless of the current index (or lack thereof). When entering invoices (on a completely different form--we do use a browse for data entry there), it's likewise 3-6 seconds between hitting ctrl+enter on one line and when the next line is available to type in.
We currently have five win XP machines and three win 7 machines that use the database. All three Win 7 machines run the form beautifully. Four out of the five XP machines choke--and I didn't bother testing the fifth. I don't think it's a hardware related difference, but for the sake of comparison:
Computer #1--Way too slow:
Intel Core 2 Duo E8400 (3.0GHz)
3GB RAM
Gb ethernet
Network optimized database
Windows XP Pro 32-bit
Computer #2--Just great:
Intel Core 2 Duo E7500 (2.9GHz)
3GB RAM
Gb ethernet
Network optimized database
Windows 7 Pro 32-bit
Both computers are connected to the same Gb network switch. The real database files reside on another Core 2 Duo Win 7 machine on the same Gigabit switch. Currently we only have 3 users on the database at any given time, although it is usually open on five different workstations at once.
Ok, sorry for such a long post, but I figured I may as well give all the info up front. So here's the bottom line: Why such a performance hit under XP? Any suggestions on how to remedy the problem?
Thanks in advance!
~Jason
Comment