AI Search
Classic Search
 Search Phrase:
 Search Type:
Advanced search options
 Search in Forums:
 Search in date period:

 Sort Search Results by:

Filter by custom fields

Topic prefix

AI Assistant
Notifications
Clear all

[Closed] I opened my forum to the public and it slowed down

3 Posts
2 Users
0 Reactions
1,668 Views
Posts: 21
Topic starter
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
(@alber)
Eminent Member
Joined: 6 years ago
[#13972]

Hi!

About 40 people connected and the forum took a long time to load.

Some people didn't directly load it and it gave database error

Can you help me please? 🙁


2 Replies
Posts: 993
Moderator
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
(@martin)
Support Team
Joined: 10 years ago

Hi @alber,

What is your hosting server parameters? Are you sure you use an appropriate hosting plan?

1. Can you take a screenshot of your Dashboard > Tools > Site Health admin page?

2. Use your hosting cPanle > phpMyAdmin Database manager and check tables with _wpforo_ prefixes. Make sure they are all use InnoDB table engine:

3. Read this instruction: https://wpforo.com/community/faq/forum-is-slow/


1 Reply
(@alber)
Joined: 6 years ago

Eminent Member
Posts: 21
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian

@martin Thanks, now is corrected!


Share: