Normalizing Performance

  • Comments posted to this topic are about the item Normalizing Performance

  • All too often performance is only considered after release. Even when it is considered more it quite often doesn't get measured until business acceptance testing. Of course, by then it is often too late such as a fundamental design of the database or component schema. Often the flexibility touted by developers only exists in the form of a complicated framework where too many shortcuts have occurred for it to be effective any longer.

    Gaz

    -- Stop your grinnin' and drop your linen...they're everywhere!!!

  • The company and clients I work for don't run SQL Server on massive hardware, mainly due to the SQL Server licensing costs for large numbers of cores. Even much of the ETL work is done outside of SSIS to avoid the Redmond tax. So these benchmarks are worthless unless they scale to the modest machines that we run.

  • I'll also add that I've seen many well intentioned good folks spend a huge wad of money on brand new servers with tons of memory and very high performance SANs, etc, etc, only to find out that they don't get very much out of it because of the way code (front-end and at the database level) was written. It can be a real killer because, typically, you only have money to buy new hardware or fix old code but not both.

    "Make it work, make it fast, make it pretty... and it ain't done 'til it's pretty." 😉

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • Jeff Moden (11/16/2014)


    I'll also add that I've seen many well intentioned good folks spend a huge wad of money on brand new servers with tons of memory and very high performance SANs, etc, etc, only to find out that they don't get very much out of it because of the way code (front-end and at the database level) was written. It can be a real killer because, typically, you only have money to buy new hardware or fix old code but not both.

    "Make it work, make it fast, make it pretty... and it ain't done 'til it's pretty." 😉

    Ah, the "let's skip the performance analysis step" trick!!!

    Gaz

    -- Stop your grinnin' and drop your linen...they're everywhere!!!

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply