Speed of go card database

[ozbob]

Howdy,

Anyone noticed a slowing down of the response times of the database backend for the go card online history etc.?

Seems to be taking longer and longer as time GOes on ...

[stephenk]

Lets hope they know how much is left in their table space!

[#Metro]

Oh no! My card had better not die again. 

[Astro]

Hi Ozbob, Yes I have noticed it takes ages to load & it seems to be getting worse. I have a page load time counter addon in my browser & after one minute I give up. I have also used a stopwatch to make sure, same result. Is this being fixed or more to the point can it be fixed?

[shiftyphil]

Is this being fixed or more to the point can it be fixed?

99.99% of developers and system administrators have NFI how to tune a database. They have to find one that does.

[ozbob]

Thanks for feedback  , anyone else noticed delays?   Might be time to ramp up the resources??

[Otto]

Just checked mine and only waited a couple of seconds for the data to show.. I checked 3 different accounts with the same 2 second delay.

However, last week there was quite a long delay as I waited for the data to appear..

[dwb]

Nope, haven't noticed it getting slower, but I am always frustrated that it can't just automatically show me last 20 and save me several clicks and extra time waiting!

[STB]

I've checked mine just now and it loaded within 2 seconds.  Overall, I haven't really notice a slowdown.

[ozbob]

Log in fine, navigate to history fine, time taken to retrieve last 20 transactions ... 38 seconds.  That is slow.

[stephenk]

Log in fine, navigate to history fine, time taken to retrieve last 20 transactions ... 38 seconds.  That is slow.

Has broadband reached Oxley yet? 

[colinw]

3 seconds for me.  (On good broadband, behind corporate firewall via a proxy server).

Will repeat from home later.

[ozbob]

Now this is getting interesting!

Just checked Mrs Ozbob's card online (she lets me, isn't that nice   )  time to retrieve history 3 seconds!

So I checked my history, time to retrieve history 39 seconds!  So clearly not a bandwidth/speed issue.

It is seems my history is in a 'special place' ... LOL

It sort of begs the question though, why is everyone else rapid but my little old go card takes a while?

[somebody]

Now this is getting interesting!

Just checked Mrs Ozbob's card online (she lets me, isn't that nice   )  time to retrieve history 3 seconds!

So I checked my history, time to retrieve history 39 seconds!  So clearly not a bandwidth/speed issue.

It is seems my history is in a 'special place' ... LOL

It sort of begs the question though, why is everyone else rapid but my little old go card takes a while?

Probably the sheer volume of transactions on your card.

[ozbob]

Probably the sheer volume of transactions on your card.

Possibly, but it shouldn't matter, and in any case only the last 60 days is live in anycase?

[somebody]

Probably the sheer volume of transactions on your card.

Possibly, but it shouldn't matter, and in any case only the last 60 days is live in anycase?

Some computer techos I work with sometimes talk about the difference between what "should" happen and what actually happens!

Just because only the last 60 days is visible doesn't necessarily mean that older info is no longer there.

[brismike]

Just tried mine and I got a respnse in 3 to 4 seconds. 

Bob . . The  reason yours is taking 39 seconds is because they are triple checking all calculations before displaying them to you.

They know who you are lol. 

[colinw]

Hmmm ... makes me wonder if there is a badly designed query or table structure in there somewhere.

I write software for a living, and know only too well how easy it is to create a badly designed algorithm that exhibits exponential degradation of performance with linear increase of data size.

[brad C]

Ozbob
You are not alone.
I generally look at the last 20 transactions and it takes on average 40 seconds.
I wondered if the time had anything to do with it - you know peak use of the system etc.
However even a check at home late at night does not resolve the issue.
No different on either work or home computer.
"Vee are vatching you comrade"!!

[p858snake]

That is probably the query they are using to retrieve the data, In most database management systems, you need to pull all the data then apply any filters (such as grouping/ordering/last X/where X is Y) after its grabbed the data, add some badly designed tables and indexes/keys in and you a issue brewing.

[Derwan]

I just tried the last 20 transactions and it took just over a minute. 

[ozbob]

In view of the system presumably being upgraded Friday evening, I just checked the history retrieval times.  Last 20 transactions:

Mrs Ozbob  2 seconds

Mr Ozbob  22 seconds  - minor improvement.  Consistent times checked early this morning, same time.  Most punters would have been zzzzzzzz