Download full result is too slow

Get Help
1

Installed version 0.41.2 ("clean" install, not upgrading old version)
When i try "save query results to xlsx(or csv)" its look like metabase again run query instead of just saving already received data. (time of query and time of "saving result" are the same)
Earlier we used version 0.35.* and don't have same trouble.

I find here solution "upgrading java to 11 from 8" but i already have isntalled java 11
Logs in metabase have only info about starting
Is there any advice?

{
  "browser-info": {
    "language": "ru-RU",
    "platform": "Win32",
    "userAgent": "Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0",
    "vendor": ""
  },
  "system-info": {
    "file.encoding": "UTF-8",
    "java.runtime.name": "OpenJDK Runtime Environment",
    "java.runtime.version": "11.0.13+8",
    "java.vendor": "Eclipse Adoptium",
    "java.vendor.url": "https://adoptium.net/",
    "java.version": "11.0.13",
    "java.vm.name": "OpenJDK 64-Bit Server VM",
    "java.vm.version": "11.0.13+8",
    "os.name": "Linux",
    "os.version": "3.10.0-1160.49.1.el7.x86_64",
    "user.language": "en",
    "user.timezone": "Europe/Moscow"
  },
  "metabase-info": {
    "databases": [
      "db2",
      "mysql"
    ],
    "hosting-env": "unknown",
    "application-database": "mysql",
    "application-database-details": {
      "database": {
        "name": "MySQL",
        "version": "5.7.36"
      },
      "jdbc-driver": {
        "name": "MariaDB Connector/J",
        "version": "2.6.2"
      }
    },
    "run-mode": "prod",
    "version": {
      "date": "2021-11-09",
      "tag": "v0.41.2",
      "branch": "release-x.41.x",
      "hash": "ad599fd"
    },
    "settings": {
      "report-timezone": "Europe/Moscow"
    }
  }
}
2

Hi @user123
You should upgrade immediately to a newer release: https://github.com/metabase/metabase/releases

Metabase does not cache the results for exports, and never has:
https://github.com/metabase/metabase/issues/8616 - upvote by clicking :+1: on the first post

I'm guessing that the problem is likely your third-party db2 driver, which is the problem, but it's difficult to tell with no more details or logs.