Hello Last year we setup a 2.60 UP with firewall, DMZ and SSL security over the Internet. It was a really painfull experience. It worked fine out of the box over the intranet, but the authentification method we had to deploy because of the DMZ was far from simple. Now it is running fine, but with one big problem: it is very slow (about 10 seconds to get a customer listing). I assume the bootleneck is SSL and the firewall, but I’d like to hear other experiences about UP speed. Toni Toni
Hello Toni, we have tested the UP with LAN and WAN connections and found out, that every page-refresh transfers 100 … 200 KByte to the client. With a slow connection this will take several seconds. Hartmuth
You can try running the dataport manually to see how long it is taking to generate the output. Your user authentication could also be taking a long time to lookup the user. CPU speed on the IIS server should be fast - according the Navision A/S this is where the biggest bottleneck will be. That processor is responsible for going through the whole rendering process. Your customer listing benchmark does sound slow. Django
Hi again The CPU is very important because of the xml+xsl->html route, but it works fast enough over the LAN. So the problem must be in the data amount downloaded to the client. I was not aware of the 100…200 KB per page benchmark that Hartmuth pointed out. So if someone has to setup UP over the internet, be sure to have a really fast connection. Toni