As you point out in the article, we should consider the performance implications of this. Perhaps we can provide a logger that doesn't write to file system but maybe sends the message off node for processing using a lightweight networking framework.
We should consider the implication of lost log statements or out of order log statements as I guess log4j does not guarantee statements are written to disk. (It will be a background thread and won't be synced at a guess).