Results 1 to 6 of 6
  1. #1
    Join Date
    Mar 2005
    Posts
    55

    Unanswered: Help with system requirements

    I know this is not the ideal setup for Access but it is necessary for the moment.

    I have 600000 records and a large amount of queries that run from this data. I need to know what the basic system requirements will be for the queries to run quickly.

    Its all indexed and normalised

    current memory 2gig
    ample drive space


    woudl increasing memory to 3 or 4 gig improve query runnign speed or will i need to get better CPU?

  2. #2
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    If Access is the only thing running, then adding RAM over 2GB might not do much, but increasing RAM generally increases system performance overall, and RAM is cheap, so go for it and find out would be my approach.

    Query design might have the biggest impact though.
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!


    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

  3. #3
    Join Date
    Nov 2004
    Location
    out on a limb
    Posts
    13,692
    Provided Answers: 59
    depending on what OS you are using.. adding additional RAM may be a benefit
    however standard XP can address (IIRC) around 4Gb
    however whether tyou will be able to use all that I don't know
    if the computer already has 2Gb RAM and a fairly recent CPU then I'd suggest you look elsewhere for performance / speed enhancements.

    I'd want to check why the system is running slow (if its running slow at all), before slinging money at it. Although memory is cheap there is no point chucking in more memory if say for example the process is CPU tied. And you don't say what processor you have got. if its running on a network I'd wnt to check if there are network bottlenecks. chucking cash at the hardware is often a seemingly attractive solution (after all virtually none of us EVER write non optimal code) so if its running slow then it MUST be the hardware thats at fault not the software..... as if

    I'd suspect the real performance benefit is going to come from your queries, table design, indexing strategies, types of join and so on...

    One other thing to bear in mind is that different windows versions have different memory abilities. IIRC standard XP can use just over 2Gb, XP professional, server and 64 bit can use more but require special configuration. if the processor cannot directly address the memory it can be configured as a virtual disk
    I'd rather be riding on the Tiger 800 or the Norton

  4. #4
    Join Date
    Feb 2004
    Location
    One Flump in One Place
    Posts
    14,912
    I believe XP can address 4GB but can only allocate up to 2GB to the VAS (IIRC).

    Show us the table structure (all indexes etc) and some queries. Is this data pretty static or changing (inserts, updates etc)? Are the queries typically returning singletons or big data sets?
    Testimonial:
    pootle flump
    ur codings are working excelent.

  5. #5
    Join Date
    Nov 2004
    Location
    out on a limb
    Posts
    13,692
    Provided Answers: 59
    Im pretty certain the addressing limit is version specific.. the 'home' version cannot address upto 4Gb (I'm pretty certain the same limit is imposed in Vista as well)
    I'd rather be riding on the Tiger 800 or the Norton

  6. #6
    Join Date
    Jan 2007
    Location
    UK
    Posts
    11,434
    Provided Answers: 10

Posting Permissions

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