Thread about block sizes

An interesting question from sejasp on blocks sizes …

A five-times improvement in i/o performance, just by changing a block size? It's the sort of thing that ought to be making the hairs on the back of your neck rise.

UPDATE: April 23rd

Well the thread has morphed into the issue of whether it is appropriate/rude/presumptious of a person to ask questions of the original poster in a forum thread.

My opinion, which I think I state pretty clearly there, is based on the following:

  • A person has asked a question in a public forum, requesting advice.
  • As their question stands, it offers the possibility of a number of different answers, and some of the answers may be inappropriate.
  • Erm … that's it.

The most appropriate answer for the situation may be, "I do not think that any action is required here … what you perceive as a problem does not in my opinion justify any corrective action." You know that's advice that I've given quite frequently. Here's some examples of questions to which the answer is "Do Nothing"

  1. My data warehouse application is not using bind variables … what should I do?
  2. I have a number of indexes with more than 120 extents … how should I reduce this?
  3. My buffer cache hit ratio has dropped below 99% to 97% … help!

So under these circumstances, can anyone tell me what is wrong with probing for more information? Especially when you are giving free advice.

UPDATE: 24th April

Thanks for the nice thoughts there, fellas. Much appreciated.

UPDATE: 25th April

Happy ending — see, I knew sejasp was a good bloke on account of being an Aussie. I have about nine great relatives over there (mostly poaching, but a little light larceny also).

Hey, just jokes fellas. Happy ANZAC day. (Is that appropriate? Is ANZAC day potentially a happy thing? comments welcome, as always)


7 thoughts on “Thread about block sizes

  1. I am not too convinced that the guy has a good handle on i/o measurement and what he hopes to achieve. It may be more realistic for him to query his table (well, his development version of it) rather than a select * on ALL_OBJECTS. The bulk of his queries could just be targeted at single rows and (to my mind) bigger block size may not be a great help here.

    (bet you can tell that I don’t do OLTP!)

  2. Indeed. The test is very obscure, but I also had the thought that he might be querying both the original system view and a copy of it’s data, or two copies of it, otherwise this would have to be two completely different databases.

    And yes, I think that a lesson on 10046’s is in order down the road.

  3. David
    There is ABSOLUTELY nothing wrong with probing for more information before answering a question. At the most basic level you are validating that you understood the question; you also are demonstrating that you are THINKING about the question and your response. It also shows that you aware that there may not be a ‘one-size-fits-all’ or “magic bullet” answer for the question.
    I would much prefer to be asked further questions to help me get to viable solution then to be ‘lead up the garden path’ as the expression goes.

  4. Dave,

    Of course there is nothing wrong with “probing for more information”, in particular when there is a reasonable doubt that the original poster is a beginer (“No we dont use parallel query and to top it up, I or anyone in here isn’t familiar with that term.”) and that some basic concepts might not be 100% clear to him/her. It is widely accepted technique in forums, we all use it all the time. I take it that DB has simply lost his temper with your persistence aim to provide the help *in high technical level* for the posters in his forum – the one thing that he and his consultants simply can’t provide.

  5. Amazing. It’s just amazing to see what kinda moron DKB can be at times (which is like 99.99% of the time).

    I see that DKB kinda skunked away after a few of the other posters jumped to your defense there.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s