Skip to main content ↑ ↓
Load time achievement Started by Ant59 · · Read 4683 times 0 Members and 3 Guests are viewing this topic.

Load time achievement

I just thought I'd share this here, as I'm quite happy with the results I'm achieving even with a fully responsive, CSS-heavy theme on top of Elkarte.



Here's the waterfall with plenty of SPDY magic :P



495 milliseconds to page load. 504 ms to full completion.
Last Edit: November 19, 2014, 10:15:51 am by ant59

Re: Load time achievement

Reply #1 –

Thats a fantastic job you are doing, very impressive !!

Re: Load time achievement

Reply #2 –

Impressive, congrats!
sorry for my bad english

Re: Load time achievement

Reply #3 –

2.0 Beta 1 is way slower... Too buggy to me...

Re: Load time achievement

Reply #4 –

Screenshot 2026-08-01 105301.jpg I tried it on this site.  It varies from run to run which is server speed I guess, but got good numbers.  What more are you expecting?
Last Edit: August 01, 2026, 05:53:21 pm by Spuds
Its me Its me, its RVD

Re: Load time achievement

Reply #5 –

Nope, the released one is the buggy one, not this site. Queries take more than 3 seconds while 1.1 is just 0.03. So yeah, I have tested, compared them and its definitely buggy.

Re: Load time achievement

Reply #6 –

For clarity, this site is running the released beta version:man_shrugging:

Re: Load time achievement

Reply #7 –

One thought is to try the "Disable hostname lookups" as that is often slow, especially on development boxes.

Re: Load time achievement

Reply #8 –

I may have posted in wrong topic but I am still talking about the buggy thing in Elkarte 2.0 beta 1, still about load time, but only in terms of its queries. Yes, I was not actually talking about Pagespeed or GMetrix site assessment, but the queries in comparing it with 1.1, which is a big difference.

Attached below are the images to ease explanation.
queries-2.0 beta 1.png
queries-1.1.10.png

However, after researching, I realized the difference is because this beta version cannot use "localhost" to connect to database like 1.1, but instead requires "127.0.0.1", for it to work.

Quotelocalhost: Often forces a local Unix socket or named pipe connection, which bypasses the network stack entirely and runs very fast (0.03 seconds).

127.0.0.1: Forces an IPv4 TCP/IP loopback connection, which goes through the network layer.

I installed both in the same server, same nginx with http3 quic setup, in the one ISPConfig, but I could not find fault on my side except that, so I really think this is a bug.

Re: Load time achievement

Reply #9 –

Quote from: "Hj Ahmad Rasyid Hj Ismail" – However, after researching, I realized the difference is because this beta version cannot use "localhost" to connect to database like 1.1, but instead requires "127.0.0.1", for it to work.


Huh?

Where you get that from?
My site is running beta and set to localhost for database connection.

Re: Load time achievement

Reply #10 –

I will retry, but last time it was not working, and I have to use 127.0.0.1. Anyway, queries delays are facts, whether or not localhost vs 127.0.0.1 was the main issue or otherwise not.

Edited: Changing it to localhost definitely causing error 500 issues. I've just re-tried. 1.1 is using localhost just fine as mentioned earlier, so not my server issue.
Last Edit: August 02, 2026, 12:02:05 pm by Hj Ahmad Rasyid Hj Ismail

Re: Load time achievement

Reply #11 –

That is strange.  

This site is on a ispconfig control panel, mariadb, apache and connects via localhost in the admin panel.  What happens when you are at the command line and try to connect with mysql -h localhost -u youruser -p and then mysql -h 127.0.0.1 -u youruser -p  to see if you get a socket or permissions error.

Re: Load time achievement

Reply #12 –

Via terminal, both connected to database just fine, so this has become more mysterious to me, but if I changed 127.0.0.1 to localhost in the Settings.php, internal server error 500 occurred, so I am not so sure, except to assume the bug is on Beta 2 from this error.log:
Code: [Copy]
tail -f /var/www/clients/clientXX/webYY/log/error.log
#1 /web/sources/ElkArte/Database/AbstractQuery.php(539): ElkArte\Database\Mysqli\Query->executeQuery()
#2 /web/sources/ElkArte/Database/Mysqli/Connection.php(54): ElkArte\Database\AbstractQuery->query()
#3 /web/sources/database/Database.subs.php(73): ElkArte\Database\Mysqli\Connection::initiate()
#4 /web/sources/Load.php(1261): database()
#5 /web/bootstrap.php(358): loadDatabase()
#6 /web/bootstrap.php(90): Bootstrap->bringUp()
#7 /web/bootstrap.php(66): Bootstrap->bringUpBasics()
#8 /web/index.php(41): Bootstrap->__construct()
#9 {main}
  thrown in /web/sources/ElkArte/Database/Mysqli/Query.php on line 165" while reading response header from upstream, client: xxx.xxx.xxx.xxx, server: elkarte2.sch .my, request: "GET / HTTP/2.0", upstream: "fastcgi://unix:/var/lib/php8.4-fpm/webYY.sock:", host: "elkarte2.sch.my"
Last Edit: August 02, 2026, 11:44:05 pm by Hj Ahmad Rasyid Hj Ismail

Re: Load time achievement

Reply #13 –

Interesting ...

So it is initializing the connection mysqli_init() and then making a successful connection with real_connect() but fails trying to do a SET NAMES UTF8 

The actual error message would have been a couple of lines about the start of that tail, so if you could post that it would be a useful clue.

Re: Load time achievement

Reply #14 –

You mean in Elkarte 2.0 Beta 1 forum? I will retry and report later.