26 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,088

Re: iRedApd bottleneck?

broth wrote:

BTW: DESCRIBE shows that the new index would be a candidate to get used but existing "account" index is used instead.

I'm aware of this, and mentioned this in post #18 in this thread.

Looking forward to your further investigation.

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

27 Reply by broth

  • broth
  • Member
  • Offline
  • Registered: 2012-04-22
  • Posts: 145

Re: iRedApd bottleneck?

ZhangHuangbin wrote:

Looking forward to your further investigation.

My investigation is stuck because conn.execute is taking most of the time.

I was playing around with SQL_ENGINE.. setting in settings.py but the only alkternative "mysql+mysqldb" is not working.

Have you any ideas about where to continue the investigation?

Thanks!

28 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,088

Re: iRedApd bottleneck?

Probably caused by Python SQL driver. Which one do you use now?
On Debian 10, try to install package "python3-mysqldb", add/update parameter SQL_DB_DRIVER in /opt/iredapd/settings.py, then restart iredapd service.

SQL_DB_DRIVER = "MySQLdb"