"new Processwire()" call needs about 1s

[chrizz]

Hello together!

I am working on a new site with pw. It is just a little gallery site. In the past I used MODx for this but since version 2 (Revolution) this CMS is pretty oversized and extremly slow. So I decided to give it a try with pw. So far so good.

On my local dev environment a basic page needs about 1.1s to get delivered by the server (only html). A short and superficially check (= end_ts - start_ts) has shown that "new Processwire()" took approx. 1s. Is this a "normal" loading time or is there any space for performance improvements. Imho 1s seems a little long... :/

Thanks guys!
Chris


#UPDATE

well... next time I should dig a little deeper: It is a documented problem within MySQL. Mysqli needs about 1 second to connect to the database:
http://www.borngeek.com/2011/04/05/mysql-performance-and-localhost-performance/

A switch from dbHost = 'localhost' to '127.0.0.1' fixed this problem.

[Martijn Geerts]

10 getResource calls take the same amount of time as getting 10.000 pages in ProcessWire.

[kongondo]

10 getResource calls take the same amount of time as getting 10.000 pages in ProcessWire.

Is this for real?

[chrizz]

kongodo, I have never tested it, but in my personal opinion PW seems to be much faster than MODx

[kongondo]

kongodo, I have never tested it, but in my personal opinion PW seems to be much faster than MODx

That I can vouch for. I spent a long while with MODX before I moved here...then again you may know that already ;-)

[Martijn Geerts]

Is this for real?

Never did a comparison, but hell ya getResources was slow. Without cache, I was ashamed to deliver it to customers.

[kongondo]

Yeah, I recall those discussion and all sorts of workarounds..