• IP addresses are NOT logged in this forum so there's no point asking. Please note that this forum is full of homophobes, racists, lunatics, schizophrenics & absolute nut jobs with a smattering of geniuses, Chinese chauvinists, Moderate Muslims and last but not least a couple of "know-it-alls" constantly sprouting their dubious wisdom. If you believe that content generated by unsavory characters might cause you offense PLEASE LEAVE NOW! Sammyboy Admin and Staff are not responsible for your hurt feelings should you choose to read any of the content here.

    The OTHER forum is HERE so please stop asking.

Forum going to uplorry soon...

You mean this?

Yes
 
@duluxe and his 'alliance' of lady boys

250px-Kathoey.jpg

Anda tak tau malu?
 
It's only common for popular sites to be subjected to scams and extortions.

ULTIMATELY, it lays upon the RESPONSIBILITIES of the website host.....

While SBF collects no IP addresses, the webhost DO have information on such, more so on these recent attacks after demanding money from boss Sam after obtaining his password and name on his website host, which FAILED.

While the moron hacker may attack SBF with DOS tactics, the website host WILL have information on WHO and WHERE those DOS attacks came from, even if those hackers will use every attempt to HIDE where they came from, as EVEN VPN cannot hide IP addresses from ghost/remote computers....

It is only a matter of RESPONSIBILITY from Boss Sam's webhost, TO IDENTIFY such IP addresses, and shut them down thru BLOCKING of their IP addresses, as such are their signatures such as by the VOLUME of attack that they had attacked, as while SBF is a popular site, it will not attract THAT MUCH volume to SBF servers.

Should SBF webhost failed to do so, then Boss Sam may reconsider another webhost, as it is only FREE MARKET at play....WITH RESP:ONSIBILITIES to Consumer....should the webhost think it is only just one customer and negligible, word of mouth TO OTHERS WILL END their FERRARI and IBIZA retirement dreams...
 
Forum is slow, like the content in the forum. We don’t deserve a hero like hwz. Speedy and require authentication.
 
so, wat's caused the bottleneck ?

The PHP parameters set when the new server was being configured.



1. Primary Tweaks: PHP-FPM Pool Settings (Most Important)Edit your pool config (usually /etc/php/*/fpm/pool.d/www.conf or similar).Core parameters to adjust:
  • pm = static (recommended for performance on a dedicated forum server)
    Fixed number of always-ready workers. Avoids spawn/kill overhead. Great when you have enough RAM.

    linuxblog.io
  • pm = dynamic (alternative if RAM is tighter)
    More flexible but adds overhead.
  • pm.max_children — This is the #1 thing to increase
    How many simultaneous PHP scripts can run.
    Rough calculation: (Available RAM for PHP in MB) / (Average PHP process size in MB).
    Monitor with ps -ylC php-fpm --sort:rss or htop to see real usage per process (often 50-150+ MB with XenForo + OPcache).
    Start conservatively and raise while watching memory. Many XenForo users go 50–200+ depending on server size.

    talk.plesk.com
  • For dynamic:
    • pm.start_servers ≈ CPU cores × 2–4
    • pm.min_spare_servers ≈ CPU cores × 1–2
    • pm.max_spare_servers ≈ CPU cores × 4
  • pm.max_requests = 500–2000+ (or 0 for static if no memory leaks). Prevents memory bloat over time.
2. Other PHP Settings
  • memory_limit = 256M–512M (XenForo can need this for some operations).
  • max_execution_time = 30–60 (don't set too high).
  • Realpath cache: realpath_cache_size=4096K, realpath_cache_ttl=600.
 
The PHP parameters set when the new server was being configured.



1. Primary Tweaks: PHP-FPM Pool Settings (Most Important)Edit your pool config (usually /etc/php/*/fpm/pool.d/www.conf or similar).Core parameters to adjust:
  • pm = static (recommended for performance on a dedicated forum server)
    Fixed number of always-ready workers. Avoids spawn/kill overhead. Great when you have enough RAM.

    linuxblog.io
  • pm = dynamic (alternative if RAM is tighter)
    More flexible but adds overhead.
  • pm.max_children — This is the #1 thing to increase
    How many simultaneous PHP scripts can run.
    Rough calculation: (Available RAM for PHP in MB) / (Average PHP process size in MB).
    Monitor with ps -ylC php-fpm --sort:rss or htop to see real usage per process (often 50-150+ MB with XenForo + OPcache).
    Start conservatively and raise while watching memory. Many XenForo users go 50–200+ depending on server size.

    talk.plesk.com
  • For dynamic:
    • pm.start_servers ≈ CPU cores × 2–4
    • pm.min_spare_servers ≈ CPU cores × 1–2
    • pm.max_spare_servers ≈ CPU cores × 4
  • pm.max_requests = 500–2000+ (or 0 for static if no memory leaks). Prevents memory bloat over time.
2. Other PHP Settings
  • memory_limit = 256M–512M (XenForo can need this for some operations).
  • max_execution_time = 30–60 (don't set too high).
  • Realpath cache: realpath_cache_size=4096K, realpath_cache_ttl=600.
sammy.com is not the only 1... lately several companies here oso having issues with their websites.. don't know wtf is going on...
 
The PHP parameters set when the new server was being configured.



1. Primary Tweaks: PHP-FPM Pool Settings (Most Important)Edit your pool config (usually /etc/php/*/fpm/pool.d/www.conf or similar).Core parameters to adjust:
  • pm = static (recommended for performance on a dedicated forum server)
    Fixed number of always-ready workers. Avoids spawn/kill overhead. Great when you have enough RAM.

    linuxblog.io
  • pm = dynamic (alternative if RAM is tighter)
    More flexible but adds overhead.
  • pm.max_children — This is the #1 thing to increase
    How many simultaneous PHP scripts can run.
    Rough calculation: (Available RAM for PHP in MB) / (Average PHP process size in MB).
    Monitor with ps -ylC php-fpm --sort:rss or htop to see real usage per process (often 50-150+ MB with XenForo + OPcache).
    Start conservatively and raise while watching memory. Many XenForo users go 50–200+ depending on server size.

    talk.plesk.com
  • For dynamic:
    • pm.start_servers ≈ CPU cores × 2–4
    • pm.min_spare_servers ≈ CPU cores × 1–2
    • pm.max_spare_servers ≈ CPU cores × 4
  • pm.max_requests = 500–2000+ (or 0 for static if no memory leaks). Prevents memory bloat over time.
2. Other PHP Settings
  • memory_limit = 256M–512M (XenForo can need this for some operations).
  • max_execution_time = 30–60 (don't set too high).
  • Realpath cache: realpath_cache_size=4096K, realpath_cache_ttl=600.
so it wasn't some ddos attack by PAP IB claimed by a samster here. LOL.
 
The PHP parameters set when the new server was being configured.



1. Primary Tweaks: PHP-FPM Pool Settings (Most Important)Edit your pool config (usually /etc/php/*/fpm/pool.d/www.conf or similar).Core parameters to adjust:
  • pm = static (recommended for performance on a dedicated forum server)
    Fixed number of always-ready workers. Avoids spawn/kill overhead. Great when you have enough RAM.

    linuxblog.io
  • pm = dynamic (alternative if RAM is tighter)
    More flexible but adds overhead.
  • pm.max_children — This is the #1 thing to increase
    How many simultaneous PHP scripts can run.
    Rough calculation: (Available RAM for PHP in MB) / (Average PHP process size in MB).
    Monitor with ps -ylC php-fpm --sort:rss or htop to see real usage per process (often 50-150+ MB with XenForo + OPcache).
    Start conservatively and raise while watching memory. Many XenForo users go 50–200+ depending on server size.

    talk.plesk.com
  • For dynamic:
    • pm.start_servers ≈ CPU cores × 2–4
    • pm.min_spare_servers ≈ CPU cores × 1–2
    • pm.max_spare_servers ≈ CPU cores × 4
  • pm.max_requests = 500–2000+ (or 0 for static if no memory leaks). Prevents memory bloat over time.
2. Other PHP Settings
  • memory_limit = 256M–512M (XenForo can need this for some operations).
  • max_execution_time = 30–60 (don't set too high).
  • Realpath cache: realpath_cache_size=4096K, realpath_cache_ttl=600.
Thanks boss.
 
The PHP parameters set when the new server was being configured.



1. Primary Tweaks: PHP-FPM Pool Settings (Most Important)Edit your pool config (usually /etc/php/*/fpm/pool.d/www.conf or similar).Core parameters to adjust:
  • pm = static (recommended for performance on a dedicated forum server)
    Fixed number of always-ready workers. Avoids spawn/kill overhead. Great when you have enough RAM.

    linuxblog.io
  • pm = dynamic (alternative if RAM is tighter)
    More flexible but adds overhead.
  • pm.max_children — This is the #1 thing to increase
    How many simultaneous PHP scripts can run.
    Rough calculation: (Available RAM for PHP in MB) / (Average PHP process size in MB).
    Monitor with ps -ylC php-fpm --sort:rss or htop to see real usage per process (often 50-150+ MB with XenForo + OPcache).
    Start conservatively and raise while watching memory. Many XenForo users go 50–200+ depending on server size.

    talk.plesk.com
  • For dynamic:
    • pm.start_servers ≈ CPU cores × 2–4
    • pm.min_spare_servers ≈ CPU cores × 1–2
    • pm.max_spare_servers ≈ CPU cores × 4
  • pm.max_requests = 500–2000+ (or 0 for static if no memory leaks). Prevents memory bloat over time.
2. Other PHP Settings
  • memory_limit = 256M–512M (XenForo can need this for some operations).
  • max_execution_time = 30–60 (don't set too high).
  • Realpath cache: realpath_cache_size=4096K, realpath_cache_ttl=600.


Thanks Boss Sam, for sharing this tech info which will help others facing terroristic and criminal attacks or just innocent high viewership demand upon civilization ÀND CRITICALLY the COUNTER MEASURES nèeded....

Evidences and wise moral judgements will be needed, to serve innocents and deal with HARMFUL single minded stubborn wilfully ignorant beasts....

We Humankind will NEVER live on knees to sub-humans such as terrorists, criminals and the insane in Human skin...

Such beasts and self serving animals may think they are smart, using and ABUSING this site that Boss Sam had ALTRUISTICALLY created in the Human Right to freedom of speech, but those Animals pathetic attempts by swaying minds to their personal greed or stubborn believes and when failed, resort to drastic actions, but they are only few COMPARED to the COMBINED intelligence of 7 Billion + HUMANKIND...
 
Last edited:
Back
Top