Recent software issues causing speed problems

 
  bevans Site Admin

Location: Melbourne, Australia
Guys, now the changes have been made and a new database server installed the speed of the site appears to have been dramatically upgrade.

What is the continued experience in user land?

Regards
Brian

Sponsored advertisement

  railblogger Chief Commissioner

Location: At the back of the train, quitely doing exactly what you'd expect.
Guys, now the changes have been made and a new database server installed the speed of the site appears to have been dramatically upgrade.

What is the continued experience in user land?

Regards
Brian
bevans
Speed has improved quite significantly. Nice work, guys.
  sydnytrains Chief Commissioner

Location: McDonalds Front counter serving customers
Speed has improved quite significantly. Nice work, guys.
"railblogger"


I concur. My speed has also increased significantly.
  YM-Mundrabilla Minister for Railways

Location: Mundrabilla but I'd rather be in Narvik
Well done - much appreciated!
  s3_gunzel Not a gunzel developer

Location: Western Sydney, AU
Load time: 0.474s 39 database queries in 0.28s
Footer


Purrrrdy...
  wanderer53 Sir Nigel Gresley

Location: front left seat EE set now departed
Works well from the Uk:D
  Graham4405 Minister for Railways

Location: Dalby Qld
Excellent at present, thanks.

Load time: 0.654s 45 database queries in 0.44s 20.2mb RAM Web server load: 1.92% DB server load: Unknown 1 calls to Railpage API

Perhaps you would care to share with us the nature of the problems discovered?
  X'Trapolis-904M Deputy Commissioner

Location: Melbourne
Works fast
Thanks

Appchaty:)
  bevans Site Admin

Location: Melbourne, Australia
Excellent at present, thanks.

Load time: 0.654s 45 database queries in 0.44s 20.2mb RAM Web server load: 1.92% DB server load: Unknown 1 calls to Railpage API

Perhaps you would care to share with us the nature of the problems discovered?
Graham4405

fine tuning of the new database server helped.  Ensuring all the database was in memory and not on disk.

Michael found some slow queries in the code which helped a lot.  I am sure he can provide further information.

Regards
Brian
  s3_gunzel Not a gunzel developer

Location: Western Sydney, AU
Out of curiosity; is the DB backed up to disk, in the odd chance that your "intern" restarts the DB server to see what happens?

Just wondering.
  bevans Site Admin

Location: Melbourne, Australia
Out of curiosity; is the DB backed up to disk, in the odd chance that your "intern" restarts the DB server to see what happens?

Just wondering.
s3_gunzel

The database has a backing store which writes out the transactions logs and also writes out the data.  If the DB crashes jt can be rebuilt using the BINLOG.

Obviously being in memory it is very fast.

Regards
Brian
  michaelgreenhill Administrator That's Numberwang!

Location: Melbourne
Out of curiosity; is the DB backed up to disk, in the odd chance that your "intern" restarts the DB server to see what happens?

Just wondering.
s3_gunzel
The database tables are all InnoDB, not MEMORY. MEMORY tables do not store data on disk.

What Brian's saying is that MariaDB has been configured to keep table indexes and query results in RAM. It still commits changes to disk.
  bevans Site Admin

Location: Melbourne, Australia
Perhaps I should have said "in memory"

In any case, there is now enough memory allocated to ensure the entire database "as at today" can be moved into memory over a period if that makes sense.

Regards
Brian
  michaelgreenhill Administrator That's Numberwang!

Location: Melbourne
Well now that everything's back in order I can get back to working on the next version...
  s3_gunzel Not a gunzel developer

Location: Western Sydney, AU
Thanks guys; that makes sense
  David Peters Dr Beeching

Location: "With Hey Boy".
Yes a lot faster than it used to be. I now have to make a cup of tea before getting on, a while back I could make one while the next thread loaded. Good work to all involved though and keep up the good work as well.

Sponsored advertisement

Display from:   

Quick Reply

We've disabled Quick Reply for this thread as it was last updated more than six months ago.