Advanced Attachment System (AAS) [Deleted]

Why?
You can not say, 256 MB will be in every case the best practice. Thats not stone printed. ;)

I use also 256 MB
View attachment 176218
With this addon, and round about 45 other addons I have no trouble. So you see, 256 MB can be enough or in some cases not enough.

Did you check this with threads containing large amount of attachments (500-1000) or pages? It only happens then with me when clicking the paperclip to view the attachments.
 
Some information already:

Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.50GHz (6 processors)
16 GB Ram
PHP 7.2
MariaDB 10.2
Opcache

my.cnf
Code:
[mysqld]
performance-schema=0
ignore_db_dirs=cmsetiofiotest
local-infile=0
ignore_db_dirs=lost+found

innodb=ON
back_log = 512
max_connections = 100
key_buffer_size = 256M
myisam_sort_buffer_size = 256M
myisam_max_sort_file_size = 2048M
join_buffer_size = 256K
read_buffer_size = 256K
sort_buffer_size = 256K
table_definition_cache = 8192
table_open_cache = 4096
thread_cache_size = 256
wait_timeout = 1800
connect_timeout = 10
tmp_table_size = 256M
max_heap_table_size = 256M
max_allowed_packet=268435456
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 = 512K
bulk_insert_buffer_size = 8M
query_cache_limit = 1024K
query_cache_size = 80M
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 = InnoDB


innodb_large_prefix=1
innodb_purge_threads = 4
innodb_file_format = Barracuda
innodb_file_per_table = 1
innodb_open_files = 1000
innodb_data_file_path= ibdata1:10M:autoextend
innodb_buffer_pool_size = 8G

innodb_buffer_pool_instances = 8

innodb_log_files_in_group = 2
innodb_log_file_size = 256M
innodb_log_buffer_size = 8M
innodb_flush_log_at_trx_commit = 2
innodb_lock_wait_timeout=50
innodb_flush_method = O_DIRECT
innodb_support_xa=1

innodb_io_capacity = 600
innodb_io_capacity_max = 1200
innodb_read_io_threads = 4
innodb_write_io_threads = 4

open_files_limit=10000
[mariadb]
userstat = 0
key_cache_segments = 1
aria_group_commit = none
aria_group_commit_interval = 0
aria_log_file_size = 768M
aria_log_purge_type = immediate
aria_pagecache_buffer_size = 768M
aria_sort_buffer_size = 192M

[mariadb-5.5]
innodb_file_format = Barracuda
innodb_file_per_table = 1

query_cache_strip_comments=0

[mysqld_safe]
socket          = /var/lib/mysql/mysql.sock
open-files-limit = 8192

[myisamchk]
key_buffer = 256M
sort_buffer = 32M
read_buffer = 32M
write_buffer = 32M

[mysqlhotcopy]
interactive-timeout

[mariadb-10.0]
innodb_file_format = Barracuda
innodb_file_per_table = 1

innodb_buffer_pool_populate=0
performance_schema=OFF
innodb_stats_on_metadata=OFF
innodb_sort_buffer_size=2M
innodb_online_alter_log_max_size=128M
query_cache_strip_comments=0
log_slow_filter =admin,filesort,filesort_on_disk,full_join,full_scan,query_cache,query_cache_miss,tmp_table,tmp_table_on_disk
 
Last edited:
Getting these errors when viewing attachments from thread list (and there are many)

Edit: : Looks like this is happening with +1000 pages threads. Also in the error log the same happened after install.
What is your UserName on xenMade? Or if you don't want to write it here, please open a thread on xenMade
 
atp_attachment_extensions error when trying to create a new forum category on 2.x.

I'm sure you helped me fix this on one of my other forums before now. Please help!
 
I used this add on extensively on my xf1.5 site. It was mostly for relatively straight forward tweaks in attachment handling. Most of those I can do with currently available attachment tools. However, the PDF attachment does not seem to be available and I have been considering implementing an extension of the PDF tool. The idea would be to allow all the standard document types that are often converted to PDF files for exchange and automatically convert those to PDF with an image from the PDF displayed as a thumbnail.

Perhaps it would be possible to extend the ATTACHMENT code to have ATTACH=pdf in addition to =full and =thumb. Or, have an option that selected which attachment extensions were converted to PDF in addition to the PDF itself which was handled by AAS.

Is the software available to study (legally) so I could explore this further?
 
Top Bottom