|Okay all you bitheads. Need help calculating baud.||Kristin|
Jun 26, 2003 12:08 PM
|I get calls all the time from exasperated users who are trying to send 6 meg attachments and want to know how long it will take to send. What I need--what I can't find online--is a formula for calculating transmission time, based on the modem connection speed. We are using Exchange 2000 on the back end and Outlook 2002 on the client. I have no idea how large their packet headers/footers are and I know that makes a difference too. For all I know, the packet construction is standardized, but I've never seen it in writing.
I could figure this out if I spent a few days memorizing the 35 page serial communications white pages...but I don't feel like it. Anybody?
|ouch head hurt nm||JS Haiku Shop|
Jun 26, 2003 12:27 PM
|re: Okay all you bitheads. Need help calculating baud.||Fender|
Jun 26, 2003 3:27 PM
|why not use an FTP site? not sure how to set them up, but they are a faster alternative to send large files over email.|
|The user is on dial-up either way.||Kristin|
Jun 27, 2003 6:57 AM
|Besides, FTP introduces some serious security risks when your transferring internal company documents. That's why we deployed a secure e-mail network.|
|not easy to do||mohair_chair|
Jun 26, 2003 8:47 PM
|The best thing to do is create some benchmarks yourself. It's not easy to calculate the throughput ahead of time because there are way too many factors to consider.
The simplest thing to do is create 100K, 200K, 500K, and 1M files containing random junk. Just copy a bunch of files of any type together. Send them and see how long it takes.
|The simplest solution is usually the most practical||Kristin|
Jun 27, 2003 7:21 AM
|And for me, the most often overlooked. The first rule of troubleshooting--make sure its plugged in. :-)|
|What would Edison do?||53T|
Jun 27, 2003 1:11 PM
|The story goes that a bunch of investors and their advisors were visiting Edison in NJ, and were spending considerable time debating what the optimal volume inside a light bulb would be for long life and good light output. They were discussing heat flux and using solid calculus to model the volume of the irregular shaped light bulb. While they rambled on, Edison walked over to a bulb he had tested and knew to be good and immersed it in a graduated cylinder in the lab. He measured the displaced water and reported the results to the assembled blow-hards. The discussion was over.|
|what kind of user?||dr hoo|
Jun 27, 2003 4:36 AM
|If you are serving home users, then i would give them a standard response with speeds and times. 56k = x to y minutes per meg, 128 = w to z minutes, etc. Let them figure out what speed things are going at their end. When they see HOURS maybe they will rethink the attachment!
Six meg attachments are just WRONG!
If it is some sort of work environment, then 6meg attachments are even worse. A sends to B, then B sends to C,D and E... etc. Upload AND download for all those users wastes time. It takes a non-trival amount of time to upload large files even with a cable modem, and I don't even want to think of dial up!
I would, in that situation, set up a web based ftp site for workers to use. FTP clients are too much for many (sad as that is) but everyone can use the web. That would make things easier for the administrator in the long run.
|The stupid kind...are there any other?||Kristin|
Jun 27, 2003 7:20 AM
|No, no. I really, really like my users a lot. Really. :)
6MB is not unheard of. A one hour PowerPoint presentation will take up that much space. And transferring it becomes necessary. You tap into the age old debate: security vs. ease-of-use. VPN is still a toddler--it's not perfected--therefore we do not allow VPN from external domains. Internal documents are not shared in the DMZ or beyond. Our FTP is part of the "beyond," as it lies entirely on the internet. Users would be breaking company policy to upload an internal document to that location. There are ways to securely VPN, but they require costly hardware and software implementations. We do not roll that technology out to many people.
Internal email is an appropriate means of sending a document that contains company sensitive information. And when my user is halfway across the country at a client site, he must use dial-up to connect to the intranet.