Re: Windows testing required: Updated runtime

Hi

On Wed, Nov 15, 2017 at 5:25 PM, George Weaver <gweaver(at)shaw(dot)ca> wrote:

> Hi Dave,
>
> When released I upgraded to pgAdmin 4v2.0. I've noticed a consistent
> pattern:
>
> On a cold start its taking a long time to load. Just now, 52 seconds.
>
> After it has been started once and then restarted, time to start is 8
> seconds.
>

On my extremely slow (2GB RAM) test VM, I just got 33 seconds for a cold
start immediately following a reboot, and 10 seconds for subsequent
startups.

On my desktop machine, I got 16 seconds for a cold start immediately
following a reboot and pgAdmin installation. Warm start was about 8
seconds. I get similar results on a Windows laptop.

Could it be that you have some anti-virus software or similar that's
slowing the first start?

>
> pgAdmin 3 (v1.22) takes 3 seconds from a cold start.
>

Apples to oranges as the architecture is completely different and they're
never going to behave the same way.

>
> George
>
>
> Hi Dave,
>
> Much improved load time - 14 seconds - Windows 10 x64.
>
> When I tried to query all the rows in a table using the context menu, the
> new tab is added and can be moved to a different window, but the following
> error was generated and the window was blank.
>
>
>
> Cheers,
> George
>
> On 06/07/2017 9:59 AM, Dave Page wrote:
>
> All,
>
> I've put an interim build of pgAdmin 4 at https://developer.pgadmin.
> org/~dpage/pgadmin4-1.5-x86.exe for Windows users. This build uses a work
> in progress patch to replace the slow Qt components with ActiveQt + the
> Microsoft web browser control to significantly improve performance.
>
> The version also includes close to 100 other bug fixes and changes, most
> noticeably performance improvements in the Query Tool that make it
> significantly faster than pgAdmin 3 with large result sets, and the ability
> to open the Query Tool and Debugger in new tabs that can be dragged onto
> different windows and therefore displays.
>
> If you have the ability, please give it a test and let me know how it
> performs. There are some known issues that we're working on:
>
> - The Query Tool History view isn't rendered correctly.
>
> - Closing a tab is now detected when there's a dirty query tool window in
> it, but closing the window containing the tab is not.
>
> - Inactive tabs have no visual definition between them.
>
> - When dragging a tab, the mouse icon changes to one with a stop sign in
> it.
>
> - If you close the last tab in a child window, it doesn't close the window.
>
> - Popout alerts don't display correctly.
>
> Thanks!
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
>
> --
> Cleartag Software, Inc.
> 972 McMillan Avenue
> Winnipeg, MB
> R3M 0V7(204) 284-9839 phone/cell(204) 284-9838 faxgweaver(at)cleartagsoftware(dot)com
>
> Fast. Accurate. Easy.
>
>

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company