Karen: Ditto what Emmitt says. Your fastest remote connection is nothing compared to your local Ethernet connection.
To that, I humbly submit that the very nature of the VPN is your frustration. The CrayolaPaedia explanation: "VPN" stands for V)irtual P)rivate N)etwork. The "Private Network" referred to is quite specifically the DEDICATED physical point-to-point T1 line we bled dollars for in the '80's and '90's. About as secure as you were going to get talking to the other guys in the era before publicly-available encryption. Nobody but AT&T was truly happy with that arrangement, so cheap geeks turned to software for salvation. Think "Fake" when you hear "Virtual". The "Virtual" is that the EFFECT of a dedicated line is produced by spewing a stream of confidently encrypted data packets across the insanely insecure Internet. 'Data packet' you say. At the core of the packet is the byte (or bytes) of data you want R:Base to play with. This is what you normally think you are send across the VPN. Since that core originates on a local network, that data will typically be bundled in the local Ethernet routing and management data. So add some byte(s) overhead to the R:Base data byte. That's what you work with on your local connection. The VPN 'engine' (hardware or software) must then perform routing operations which strip away and replace this local routing information with new, remote workstation information; and then encrypts this re-routed data packet encrypted in a process which 'wraps' these bytes with encryption data so that the packet can travel the Internet. More bytes added per R:Base data byte. This package is then wrapped with the encrypted "pipeline" maintenance data which ensures that the encrypted contents are either received and not rejected, or when missed, resent; and then unbundled properly at the other end. More bytes. This then gets wrapped with the publicly visible Internet routing data that gets it there. More bytes. Simply put, that one byte of R:Base data has the aspect of a child so coated, booted, hatted, muffled and gloved that he can't throw snowballs. So the bigger the data set you draw across a VPN for remote processing, the slower the connection, the greater the number of concurrent VPN engine users, the fewer snowballs you get to throw. Makes one want to spend $1,500/month for a good old-fashioned, dedicated T1 line. I've done some violence to accuracy in this explanation, but what the heck; I'm on vacation. Hope it helps. Cheers, and Happy Thanksgiving bruce chitiea safesectors. > -------- Original Message -------- > Subject: [RBASE-L] - Re: Off topic > From: "Emmitt Dove" <[email protected]> > Date: Mon, November 22, 2010 7:37 pm > To: [email protected] (RBASE-L Mailing List) > > > Sure. When you connect at your client you probably have a 100 megabit per > second link to the server holding the database. When you run R:BASE on your > laptop and execute a SELECT you have a pretty reasonable pipeline through > which the data is moved. > > > > At home, the speed of the VPN is certainly no faster than your own connection > to the internet. If you have broadband, that is probably in the range of 2-6 > megabits per second. This is a much smaller pipeline through which the data > must move, as in 1/50th to 3/50th the speed. So if you run R:BASE on your > laptop, it will be very slow since the data has to move through a straw > instead of a 6” pipe. > > > > Now, if you RDP to the server and run R:BASE on the server desktop, the > pipeline is as big as the disk I/O subsystem in the server, with the obvious > overhead of other users, etc. That will be far faster than even the 100 mbps > connection at the client. > > > > Emmitt Dove > > Converting Systems Architect > > Evergreen Packaging, Inc. > > [email protected] > > (203) 214-5683 m > > (203) 643-8022 o > > (203) 643-8086 f > > [email protected] > > > > From: [email protected] [mailto:[email protected]] On Behalf Of > [email protected] > Sent: Monday, November 22, 2010 16:41 > To: RBASE-L Mailing List > Subject: [RBASE-L] - Re: Off topic > > > > Emmitt: I know nothing technical about VPNs, but don't understand the > significance of where the code is. For an example, if I'm at Wrigley with > my laptop connected to the network it can take 2 seconds to execute a select > command with a where clause. Take that same laptop home and connect to the > network via a VPN (so I'm not remoting into another workstation) and that > same select could take 15 minutes. Exactly what makes the VPN so slow then? > Is there an easy (non-tech) way to explain that for me? > > Karen > > > > > > Jim, > > The question to answer is, “Where is the code that is accessing the database > actually executing?” > > > > Emmitt Dove
