Welcome, Guest. Please login or register.
Did you miss your activation email?

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - alexyuisme

Pages: 1 [2] 3
16
I can only see you launched the exe in env1 in the video. So you also tried env2 and the launch speed is the same?

I tested the static build today and the speed is similarly slow. Maybe we can root out the cause of dll look-ups.

I will try disable any antivirus and let you know.

Thanks,
Alex

18
That's strange. On our side, three machines have been tested and all have the same issues.

Alex

19
BTW, what is the correct way to build static lib of limereport? I wanna give it a try.

Thanks,
Alex

20
I realy doubt it is a physical disk issue because environemnt 1 works fine.

No need to use my program because the problem exists in demo1 too. I think you can create a deployment folder for demo1 under release build.

How to reproduce:

1. restart the machine, in the deployment folder, run LRDemo_r1.exe, time the launch time as T1.
2. restart the machine, copy some extra dlls(> 20) in the deployment folder, run LRDemo_r1.exe, time the launch time as T2.

You will notice T2 is much larger than T1.

Thanks,
Alex

21
now try from command line in folder d:\test
set PATH=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;
'your_program'.exe

-> gave it a try but it doesn't solve the problem.

22
So the problem becomes much clearer now. If I put limereport-unrelated dlls in the exe directory, the launch becomes much slower.

tested the demo1/demo2 exe in release build.

Alex

23
from cammand line: D:\Qt\Qt5.12.4\bin\windeployqt d:\test\'you_exe_file'
copy to this folder limereport.dll, QtZint.dll, libgcc_s_seh-1.dll, libstdc++-6.dll, libwinpthread-1.dll

-> This is exactly what I did for environment 1: the exe takes a few seconds to launch. Not impressive but still acceptable.

If I move the exe into environment 2(our production environment) which has the same dll as environmet 1 plus other dlls, the exe takes more than 1 minutes to launch...and the harddisk is 100% taken for processing something...

It is very strange to me.

Alex



24
I noticed some environments have dlls: libGLESv2.dll and libEGL.dll but some environments don't have those two files. Are those two dlls necessary?

Thanks,
Alex

25
My Qt's install path: D:\Qt\Qt5.12.4\

26
1. please type from CMD echo %PATH% copy from & past here result

C:\Users\Administrator>echo %PATH%
C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v10.2\bin;C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v10.2\libnvvp;C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin;C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\libnvvp;C:\Program Files\Microsoft MPI\Bin\;C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.1\bin;C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.1\libnvvp;C:\Program Files\DahuaTech\MV Viewer\Runtime\x64\;C:\Program Files\DahuaTech\MV Viewer\Runtime\Win32\;C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v8.0\bin;C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v8.0\libnvvp;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;D:\Program Files\PuTTY\;D:\Program Files\TortoiseGit\bin;D:\Program Files\Git\cmd;D:\Qt\Qt5.12.4\Tools\mingw730_64\bin;D:\Qt\Qt5.12.4\5.12.4\mingw73_64\bin;C:\Strawberry\c\bin;C:\Strawberry\perl\site\bin;C:\Strawberry\perl\bin;D:\Program Files\nodejs\;D:\sqlite;D:\boost_1_70_0\tools\build\src\engine\bin.ntx86_64;D:\Program Files\Java\jdk1.8.0_221\bin;D:\Program Files\CMake\bin;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files\NVIDIA Corporation\NVIDIA NvDLISR;C:\Users\Administrator\.dnx\bin;C:\Program Files\Microsoft DNX\Dnvm\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Users\Administrator\AppData\Local\Programs\Python\Python37;C:\Users\Administrator\AppData\Local\Programs\Python\Python37\Scripts\;C:\Users\Administrator\AppData\Local\Programs\Python\Python37\Lib;D:\Program Files (x86)\Windows Kits\10\bin\10.0.17763.0\x64;D:\Go\bin;D:\Flutter\bin;C:\Program Files\TortoiseHg\;C:\Windows\SysWOW64\5097;C:\Windows\SysWOW64\5097;C:\Windows\SysWOW64;C:\Program Files\dotnet\;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.0\;C:\Program Files\Microsoft SQL Server\120\Tools\Binn\;C:\Program Files\NVIDIA Corporation\Nsight Compute 2019.5.0\;C:\Program Files\MySQL\MySQL Shell 8.0\bin\;D:\Users\Administrator\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\Administrator\go\bin;C:\Users\Administrator\AppData\Local\Programs\Python\Python37\Scripts;c:\Program Files\MySQL\MySQL Server 8.0\bin;C:\ninja;C:\Users\Administrator\.dotnet\tools

C:\Users\Administrator>

2. Please see the attachments.

Let me know if any more info is needed.

Thanks,
Alex

27
My answers:

Is the same problem when you're launch the program from build environment?

-> No, the launch speed under Qt Creator is ok. Launch speed after deployment is not ok (the launch time varies from a few seconds to more than one minutes, depending on different environments that contain different dlls.)

What version of LR you uses?
What version of QT?

-> This is my environment: Win10 64-bit, LimeReport v1.5.35, Qt-5.12.7, Mingw 7.3.0 64-bit, 8GB Ram, i5 6500 quad core cpu.

May be QT version you are used when build LR and QT version in another environment are different?

-> All environments are built with the same version of QT toolchains as listed above.

What in PATH variable of "differsnt environment"?

-> All environments use the same PATH variable which doesn't contain the paths of limereport.dll and QtZint.dll.
the executable, limereport.dll and QtZint.dll are located in the same directory for all environments.

Thanks,
Alex

28
My source code: https://github.com/alexyuisme/test_limereport.

I copied this compiled exe into different environment which contains different number of dlls and the launch time varies.(from a few seconds to more than one minutes) Is it caused by dll look-ups?

I did the same thing by copying the demo program "LRDemo_r1.exe" to different environments(with different dlls), and the launch time varies the same.

Note: limereport.dll and QtZint.dll exist in the same directory as the executable for all environments.

Any ideas?

Thanks,
Alex

29
 :-\That's my bad...After restart my machine the problem remains. Is there anyone experiencing the same slow new process?

Alex

30
Hi!
Could you explain the issue in more detail? Which OS, compiler, limreport and Qt version do you use?
I have checked the next code:
Code: [Select]
    QTime start = QTime::currentTime();
    report = new LimeReport::ReportEngine(this);
    qDebug() << start.msecsTo(QTime::currentTime());
in my demo_r1 sample project and got 528 msec in debug mode and 268 in the release.   

After some hackings, I found one possible way to speed up the init process: just kick off "report = new LimeReport::ReportEngine(this)" before main ui gets initialized. I am not sure why that works but if I put the new statement after ui initialized(like I did before), the new process is bloody slow.

Note: my ui is way more complcated than those in demo1 and demo2.

Thanks,
Alex


Pages: 1 [2] 3