furthermore, this mask is kind of pointing to a possible problem: ?1?1?1?1?1?1?1?1?1?1?1
if --custom-charset1 (or short -1) is defined with a very small number of chars (small charset), that might be the main reason why you don't get full acceleration. You should get a warning in such cases after a few seconds/minutes.
Without knowing how small/huge that keyspace is, it's very difficult to say if you can reach full acceleration.
try with a mask of ?b?b?b?b?b?b?b?b?b instead, just for the testing purpose.
also see https://hashcat.net/faq/morework
btw: single hash vs 2+ hashes makes a huge difference, because of optimizations that can only be performed when having only one hash (depends on the hash type of course)
update: according to this number 4049565169664 the --custom-charset1 only consists of 14 chars because 14^11 = 4,049,565,169,664
that's already quite small number of chars (almost like ?d = 10 digits)
if --custom-charset1 (or short -1) is defined with a very small number of chars (small charset), that might be the main reason why you don't get full acceleration. You should get a warning in such cases after a few seconds/minutes.
Without knowing how small/huge that keyspace is, it's very difficult to say if you can reach full acceleration.
try with a mask of ?b?b?b?b?b?b?b?b?b instead, just for the testing purpose.
also see https://hashcat.net/faq/morework
btw: single hash vs 2+ hashes makes a huge difference, because of optimizations that can only be performed when having only one hash (depends on the hash type of course)
update: according to this number 4049565169664 the --custom-charset1 only consists of 14 chars because 14^11 = 4,049,565,169,664
that's already quite small number of chars (almost like ?d = 10 digits)