Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 54
  • Last Modified:

Disk Imaging Calculation - How long should it take?

I've been searching for some way to calculate expected disk imaging durations but I can't find anything useful. Here's my scenario:

Mac OS X image = 16.5 GB
One (1) Client NIC = 1 Gbps
Imaging server (Deploy Studio) NIC = 1 Gbps

I would like to come up with a formula for determining what the duration should be for this one client. Then I would like to be able to add clients and see how it affects the duration.

Thanks,
-mike
0
ascendmax26
Asked:
ascendmax26
  • 4
  • 2
1 Solution
 
_Commented:
1 gig nics help, but the time it will take depends more on Sustained Throughput of the slowest storage device you are using.
The type of devices and how they are connected, will also have some impact.

ex: in the same system, using 2 IDE drives on the same channel (cable) will not be as good as 2 IDE drives on different channels (cables).
0
 
ascendmax26Author Commented:
Thanks for the input, cora147. I assume some sort of disk I/O factor - both from the client and server sides - will be part of the equation. Network throughput is only part of the picture.
0
 
_Commented:
With the 1gig nics, it (disk I/O) will probably be the biggest part. It's a fairly straight forward math problem.

Just don't forget to crank up Performance Monitor and get some real time numbers. Just to see how much (if any) lag the systems add to the situation.
What you "actually" get, doesn't always match what you "should" get according to the numbers, but you can include a "fudge" that will keep you close enough.

Have fun.   : )
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
ascendmax26Author Commented:
Doesn't sound like anyone has calculations I can use. I'm putting together my own and will share for input.
0
 
_Commented:
That's because there isn't one. It always depends on the system being used.

The main factors you need are
- file size
- listed drive i/o sustained speed
- then any "channel" limitation (IDE, SATA, SCSI, NETWORK, etc) that might come into play.

And since the actual numbers are not usually as good as the Theoretical Numbers, you need to run some actual tests to figure the "fudge" factor for that machine.

If doing a bunch of systems, that is a pita though, so as a "Rule of Thumb" I figure anything over 75% of the above TN, is good. Anything under, I might want to look into.
But that's just my little cheat.
0
 
_Commented:
Thank you much.     : )
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now