T
T
Timitu2016-03-15 20:42:44
CMS
Timitu, 2016-03-15 20:42:44

Wordpress is designed for a heavy load?

Wordpress can handle a lot of hits, databases, etc. Do you recommend doing a big project with a lot of traffic on it? Will there be problems later? If so, which ones? Thanks in advance for your reply!

Answer the question

In order to leave comments, you need to log in

6 answer(s)
M
Mr Crabbz, 2016-03-15
@Punkie

Depends solely on the capacity of the server and the directness of the hands of the developer.

I
Igor Vorotnev, 2016-03-16
@HeadOnFire

1. 100 thousand per day is not much.
2. If you take pure WP without 50+ shitty plugins, then it is very smart out of the box.
3. If you customize (plugins and hands), then everything depends on the curvature of the custom code / plugins.
A properly configured server will be inexpensive. If the site is mostly static (guest visits, no shopping cart, personal accounts, etc.) - $5-10 per month. If dynamics, users, all things - it is better to take for $20. Prices are all listed in Digital Ocean tariff plans.
Server stack:
- Nginx 1.9.* (at the time of this writing)
- PHP 7
- Memcached
- MariaDB 10.1/10.2
And a free SSL certificate from Let's Encrypt + HTTP/2 protocol on the Nginx side.
Plugins on the WP side:
- Memcached is your friend for object cache
- Fast Full-Page Cache for caching if the site is static (see above)
- WP Super Cache for caching if the site is dynamic (see above)
However, if the site is static and there is a desire to get confused - you can add in Nginx's native fastcgi_cache, which, in turn, is mounted in memory. It will be generally super-megafast and rpm such that you can withstand any habraeffect.

W
Web Developer Blog, 2016-03-15
@Alexey_Suprun

Go to the autodesk website, it is written in WordPress, see what it can be, and pay attention to the download speed

S
Syomka Gavrilenko, 2016-03-16
@cema93

Wordpress easily pulls a lot of uniques, but for this you need to do the following:
1. Make a theme manually, do not take popular ones with a bunch of unnecessary settings, but do it for yourself
2. Use only the necessary plugins, and ideally not use them at all.
3. Use caching.
I received a site that loaded a dedicated server Core i3 3.4GHz (2 cores) 4GB RAM 2x500GB SATA at 100% with 500 uniques.
I rewrote the theme from scratch, integrated all the necessary plugins into the theme and now the site is running on VDS
1 processor core 512 MB of RAM 30 GB of hard disk and only loads it by 20% with 1500 uniques.
Conclusion: Each system has its pros and cons, each system is optimized in its own way, which means that everything depends on the directness of the hands of your developer.

T
TyzhSysAdmin, 2016-03-15
@POS_troi

No, WP is not suitable for high-traffic resources.
But again, what is "big"? 1000 uniques per day? 5000? 10000? mulion?

V
Vlad Zhivotnev, 2016-03-15
@inkvizitor68sl

> then a day somewhere between 70,000 - 100,000
Little things in life, I kept such WP on 2G memory, 1 core, ssd.
Out of the box (if you do not turn on aggressive caching, but use only php opcash) on a hetzner server for 42EUR without any special settings on ssd, WP gives about 50-70 responses per second. You can tune up to 150 RPS without special knowledge using server settings.
And so, with aggressive caching - easily 2 thousand responses per second, and this is not the limit.
The main problem with WP is that many popular plugins are poorly written, frankly slow down and can decently crawl through the database. Basic WP itself cannot be called slow. There are, of course, cms and faster, but they can do less.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question