Unfortunately, the Mendix audit trail will give you this much excess. You are creating a record in audit trail for each attribute that changes in every entity you are auditing. So if your entity has 20 attributes, you are committing 21 objects to commit it. The commit on the entity itself, plus the commit of 20 audit records (maybe even more as you include the main log item plus all the log lines for attributes which have changed. Even if you switched to using an association to the log object vs. the audittrailSuperClass object, you’d still have this issue.
You can limit the audit trail to only attributes which have changed, but that doesn’t help you with a mass import where all the attributes are new, so all will get an audit record.
If possible, I’d recommend disabling the audit trail for the initial import. This will greatly reduce the import time.
I completely agree with Imran Kasam here, but here are two insights that you could use reducing the client-side duration. Unless if you opt for the first option, the whole process will still take 1.5 hours, but no user will be affected by this duration.