melroy

u/melroy@kbin.melroy.org
73 posts · 2.0k comments

Recent posts

Recent comments

Yea so the same servers and IP addresses VPN provider use (which are again just cloud providers) are also used for other purposes mainly by scrapers and DDos attacks indeed. Too bad all those cloud providers do not act accordingly in the past 5 - 10 years. Since its getting worse and worse. With the increase of datacenters and centralization, I consider it a duty of these companies to take action to stop these scammers, spammers, scrapers, and attackers.

However, that is often not the case. Now I must say, I created Angie Guardian myself (alternative to Anubis). So hopefully soon I can slowly open some of ASN bans. And see how it goes.

I block some misbehaving data centers. Which are often also used by VPN providers. So it's more collateral damage.

No I fully block some data centers not just rate limit.

  • I run 50+ websites
  • MariaDB instances
  • PostgreSQL instances
  • Docker containers
  • Mbin, Nextcloud, GitLab, GitLab runners, gitea, bitcoind, fulcrum, grafana, prometheus, influxdb, Synapse, Angie, telegraf and various other services like fail2ban etc. etc.

All optimized for performance and fine tuned as well, eg. lets say you run mariadb vs how I run it:

innodb_buffer_pool_size = 8G
innodb_flush_log_at_trx_commit = 2
innodb_log_file_size = 2G
innodb_log_buffer_size = 32M
innodb_max_dirty_pages_pct = 90
innodb_io_capacity=5000
innodb_io_capacity_max=20000
innodb_read_io_threads=8
innodb_write_io_threads=8
query_cache_type = 1
query_cache_limit = 2M
query_cache_min_res_unit = 2k
query_cache_size = 128M
tmp_table_size= 128M
max_heap_table_size= 128M

[mysqld]
max_connections = 200
character_set_server = utf8mb4
collation_server = utf8mb4_general_ci
transaction_isolation = READ-COMMITTED
binlog_format = ROW
innodb_file_per_table=1
# Increase open files based limits.conf value
open_files_limit=65535

Same idea for Postgresql.. You can run "postgres" or.. actually run postgresql in production correctly like:

shared_buffers = 6GB
work_mem = 20MB
maintenance_work_mem = 2GB
maintenance_io_concurrency = 200
max_worker_processes = 14 
max_parallel_workers_per_gather = 4
max_parallel_maintenance_workers = 4
max_parallel_workers = 12

synchronous_commit = off
commit_delay = 300

checkpoint_timeout = 30min
max_wal_size = 60GB
min_wal_size = 4GB

Not for me. I have a very quick ryzen setup with tons of ram and nvme etc. I never want back to a orange pi. But sure. I don't like waiting, as a developer myself I just want to have quick loading pages and services.

Most of these devices have very limited IO disks speeds as well as slow processors. And also limited ram.

I don't think it's a massive overkill. He most likely will try to host even some more services besides nextcloud etc.

I recommend actually to get more ram. Despite the stupid high prices I know.

I agree. The most limiting factor is still memory for me. And I'm max out currently of my motherboard (128gb).

Recently thessecond limiting factor is actually cpu. But that is due to my gitlab runners.

Well I'm banning codeberg. Whether you like crypto or LLM doesn't matter. They are censoring developers like that.

It's not up to codeberg to decide where developers are allowed to work on or which tools to use. It's the start of the end.