+ Post New Thread
Results 1 to 9 of 9
Windows Server 2008 Thread, Would this run well? in Technical; Ok, I am thinking of rebuilding this server - it has to deal with around 25 simultaneous connections and 35 ...
  1. #1
    binky's Avatar
    Join Date
    Sep 2006
    Posts
    290
    Thank Post
    1
    Thanked 19 Times in 16 Posts
    Rep Power
    0

    Would this run well?

    Ok, I am thinking of rebuilding this server - it has to deal with around 25 simultaneous connections and 35 pcs.

    SATA Hard Disks
    4GB RAM
    Dell SC445
    Dual Core Intel Xeon 3060 2.40GHz


    Running in a single server environment:

    Windows Server 2008
    Active Directory
    Windows Deployment Services
    IIS + mySQL (moodle)
    Network Access Protection

  2. #2

    Michael's Avatar
    Join Date
    Dec 2005
    Location
    Birmingham
    Posts
    9,265
    Thank Post
    242
    Thanked 1,575 Times in 1,254 Posts
    Rep Power
    341
    That sounds fine, but using Windows Deployment Services probably isn't worth it for 35 workstations. So long as the server operates at 1000Mbps and workstations 100Mbps, this should remove any bottlenecks too.

    If you're going to run Windows Server 2008 x86, don't install anymore than 3GB of memory. 4GB will be a waste of money, unless you're going to run x64?

    You also need to make sure your hard disks have enough capacity to store all data too. A minimum of two would be recommended. One as the system disk and the other for everything else.

  3. #3

    Join Date
    Jan 2006
    Location
    Surburbia
    Posts
    2,178
    Thank Post
    74
    Thanked 307 Times in 243 Posts
    Rep Power
    115
    4GB will be a waste of money
    Because? I thought (provided the hardware supported it) Windows Servers supported remapping the I/O reserved memory.

  4. #4

    SYNACK's Avatar
    Join Date
    Oct 2007
    Posts
    11,240
    Thank Post
    882
    Thanked 2,742 Times in 2,316 Posts
    Blog Entries
    11
    Rep Power
    784
    Quote Originally Posted by PiqueABoo View Post
    Because? I thought (provided the hardware supported it) Windows Servers supported remapping the I/O reserved memory.
    The feature that you are thinking of is PAE which remaps memory from a lower accessible range to the extended memory range. It will allow you to access this memory but not directly as it effectively pages between the high and low RAM ranges which is much slower than direct access.

    This Microsoft page shows more information about how much memory is supported and how it is divided up (top of page):
    Memory Limits for Windows Releases (Windows)

  5. #5
    binky's Avatar
    Join Date
    Sep 2006
    Posts
    290
    Thank Post
    1
    Thanked 19 Times in 16 Posts
    Rep Power
    0
    Well it would be an x64 server anyway.

  6. #6

    Join Date
    Jan 2006
    Location
    Surburbia
    Posts
    2,178
    Thank Post
    74
    Thanked 307 Times in 243 Posts
    Rep Power
    115
    The feature that you are thinking of is PAE
    Nope that was yesterday, but alright I'll do it again.. ;b

    which is much slower than direct access
    If it's so bad why has PAE been recommended for Exchange 2K3 for a few years?

  7. #7

    SYNACK's Avatar
    Join Date
    Oct 2007
    Posts
    11,240
    Thank Post
    882
    Thanked 2,742 Times in 2,316 Posts
    Blog Entries
    11
    Rep Power
    784
    Quote Originally Posted by PiqueABoo View Post
    Nope that was yesterday, but alright I'll do it again.. ;b



    If it's so bad why has PAE been recommended for Exchange 2K3 for a few years?
    Its not bad, just slower than directly accessing the memory using a 64bit OS. I was just giving an overview of what it is and the all be it small consequences of its use to the speed of the system.

  8. #8

    Join Date
    Aug 2005
    Location
    London
    Posts
    3,157
    Thank Post
    116
    Thanked 529 Times in 452 Posts
    Blog Entries
    2
    Rep Power
    124
    Quote Originally Posted by Michael View Post
    That sounds fine, but using Windows Deployment Services probably isn't worth it for 35 workstations.
    What??? Are you suggesting (s)he manually goes round and installs all the machines??

    WDS is free, works well and has minimal impact on the server (you can even turn off the services except when you're deploying new machines if you think it is a problem) so I can't see a reason not to use it!

  9. #9

    Join Date
    Jan 2006
    Location
    Surburbia
    Posts
    2,178
    Thank Post
    74
    Thanked 307 Times in 243 Posts
    Rep Power
    115
    Its not bad, just slower than directly accessing the memory using a 64bit OS
    Directly is not quite the right word. Pretty much everything we care about is a userland app and they use virtual memory i.e. it's indirect.

    The best fit for your concept is AWE where some greedy app needs truckloads more virtual memory than can be addressed with 32-bits, so it gets the OS to swap the extra memory it needs in and out of that limited virtual address space. Application code to manage this aside, this is essentially done by moving pointers to physical memory pages i.e. large chunks of data are not being copied from one region of memory to another.

    64-bit does save seriously memory hungry apps from having to do that kind of faffing around, although AWE memory may still get used because it never gets swapped out to the pagefile.

SHARE:
+ Post New Thread

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •