Invision Community 4: SEO, prepare for v5 and dormant account notifications Matt November 11, 2024Nov 11
April 24, 20159 yr I believe if many do the F5 refresh at the same time, they would take it down eventually, because the Cpu raised, but not enough to notice it with only one person doing it.I will research a solution for this.
April 24, 20159 yr Author I believe if many do the F5 refresh at the same time, they would take it down eventually, because the Cpu raised, but not enough to notice it with only one person doing it.I will research a solution for this.​What's your server specs, i would think it would be quiet good (or your host) because the second site of yours isnt affected at all lol
April 24, 20159 yr ​What's your server specs, i would think it would be quiet good (or your host) because the second site of yours isnt affected at all lol​The site is not mine. Its from a user here that i setup the server. Its a 4 core with 16Gb of Ram with a normal HDD.
April 24, 20159 yr Author ​The site is not mine. Its from a user here that i setup the server. Its a 4 core with 16Gb of Ram with a normal HDD.​Interesting. I have four cores too, and they get eaten up pretty good.. Are you not using any node delay etc? I guess if you really configure the database properly it will cache it and won't do faeces.
April 24, 20159 yr ​Interesting. I have four cores too, and they get eaten up pretty good.. Are you not using any node delay etc? I guess if you really configure the database properly it will cache it and won't do faeces.​No relay. Just using Centos with Apache in the Backend and Nginx as a reverse proxy. MariaDB for the database with many optimizations. Opcode cache, Memcached and that kind of things also.
April 24, 20159 yr Author ​No relay. Just using Centos with Apache in the Backend and Nginx as a reverse proxy. MariaDB for the database with many optimizations. Opcode cache, Memcached and that kind of things also.​i use plain nginx, apc + memcached and mariadb, not sure if there are anything special with my mariadb setup tho
April 24, 20159 yr Author ​No relay. Just using Centos with Apache in the Backend and Nginx as a reverse proxy. MariaDB for the database with many optimizations. Opcode cache, Memcached and that kind of things also. ​suggestion? back_log = 75 max_connections = 300 key_buffer_size = 32M myisam_sort_buffer_size = 32M myisam_max_sort_file_size = 2048M join_buffer_size = 64K read_buffer_size = 64K sort_buffer_size = 128K table_definition_cache = 4096 table_open_cache = 2048 thread_cache_size = 64 wait_timeout = 120 connect_timeout = 10 tmp_table_size = 32M max_heap_table_size = 32M max_allowed_packet = 32M max_seeks_for_key = 1000 group_concat_max_len = 1024 max_length_for_sort_data = 1024 net_buffer_length = 16384 max_connect_errors = 100000 concurrent_insert = 2 read_rnd_buffer_size = 256K bulk_insert_buffer_size = 8M query_cache_limit = 512K query_cache_size = 16M query_cache_type = 1 query_cache_min_res_unit = 2K query_prealloc_size = 262144 query_alloc_block_size = 65536 transaction_alloc_block_size = 8192 transaction_prealloc_size = 4096 default-storage-engine = MyISAM
April 25, 20159 yr ​i use plain nginx, apc + memcached and mariadb, not sure if there are anything special with my mariadb setup thoYou can setup my.conf based on your needs.
April 25, 20159 yr Your key_buffer_size seems tiny. Look for the mysqltuner.pl script which can offer suggestions based on your stats.
April 25, 20159 yr Author Your key_buffer_size seems tiny. Look for the mysqltuner.pl script which can offer suggestions based on your stats. ​[!!] Query cache prunes per day: 50640[!!] Joins performed without indexes: 244 (see join_buffer_size note below)[--] Up for: 10h 45m 55s (488K q [12.616 qps], 44K conn, TX: 1B, RX: 84M)[--] Reads / Writes: 41% / 59%[--] Total buffers: 88.0M global + 800.0K per thread (300 max threads)[--] Status: +ARCHIVE +Aria +BLACKHOLE +CSV +FEDERATED -InnoDB +MRG_MYISAM[--] Data in MyISAM tables: 40M (Tables: 354)[--] Data in PERFORMANCE_SCHEMA tables: 0B (Tables: 17)[!!] Total fragmented tables: 13Variables to adjust: query_cache_size (> 16M) join_buffer_size (> 64.0K, or always use indexes with joins)
April 25, 20159 yr Author Ah, you've only got a forum table of 40M - that's fine for now then ​I guess, curious how i could "optimize" it, to prevent 'f5' .. i cant think of much else lol
April 25, 20159 yr ​I guess, curious how i could "optimize" it, to prevent 'f5' .. i cant think of much else lol​You could for exemple convert your tables to Innodb instead of Myisam.
April 29, 20159 yr ​are you doing this on localhost? ​I have mod_security and mod_evasive installed on my server, and if i press F5, it will not take my server down, but it will rise the CPU and the board will become slower.
April 29, 20159 yr ​I have mod_security and mod_evasive installed on my server, and if i press F5, it will not take my server down, but it will rise the CPU and the board will become slower.You need to actually configure mod_evasive, not just install it. You not knowing how to configure your server to cope with DOS attacks isn't a bug. Consider Invision's could hosting service.
April 29, 20159 yr You need to actually configure mod_evasive, not just install it. You not knowing how to configure your server to cope with DOS attacks isn't a bug. Consider Invision's could hosting service. ​Its configured But the F5 is so fast, that it does not triger it. I actually can rate limit http requests using Nginx instead. But a single page can make many requests, and in the end, the page gets slower.
April 30, 20159 yr Author You need to actually configure mod_evasive, not just install it. You not knowing how to configure your server to cope with DOS attacks isn't a bug. Consider Invision's could hosting service. ​Lmao, that's a little rude. And we just explained here that we can take down this site, so whats the difference between theirs and ours? Give link to yours?
Archived
This topic is now archived and is closed to further replies.