brute_log_entries.list inefficient way of storing characters

[SEO Guru]

brute_log_entries.list entries look like:

17035567740000=attempts=%31&filter=wordpress%31&ip=%31%30%33<<<SNIP>>>%32&log=%31%30%33%2E%31%34%32%2E%32%36%2E%33%32%20%2D%20%2D%20%5B%32%36%2FDec%2F%32%30%32%33%3A%30%33%3A%31%32%3A%32%31%20%2B%30%31%30%30%5D%20%22POST%20%2Fwp%2Dlogin%2Ephp%20HTTP%2F%31%2E%31%22%20%32%30%30%20%36%38%32%39%20%22%2D%22%20%22Mozilla%2F%35%2E%30%20%28Windows%20NT%20%31%30%2E%30%3B%20Win%36%34%3B%20x%36%34%29%20AppleWebKit%2F%35%33%37%2E%33%36%20%28KHTML%2C%20like%20Gecko%29%20Chrome%2F%36%36%2E%30%2E%33%33%35%39%2E%31%31%37%20Safari%2F%35%33%37%2E%33%36%22&time=%31%37%30%33%35%35%36%37%37%34

This is a very inefficient way of storing data and easy to get a big file causing high load when dataskq runs.

Any possibility this gets improved?

 

[SEO Guru]

Just my humble thoughts about improving this.

I think the characters are encoded to avoid breaking the line/url (what it looks) structure.

You can replace breaking characters like & or = with other non breaking characters.

Or change the entire structure to be line based so every entry has a fixed amount of lines

time=
ip=
….