From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Mike Surcouf <mikes(at)surcouf(dot)co(dot)uk> |
Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>, pgAdmin Support <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: Windows testing required: Updated runtime |
Date: | 2017-07-07 08:38:54 |
Message-ID: | CA+OCxoz1eKbAxrSEhy1svaiY9Mkd-caBw3HfPPW7iH7d9ppehQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers pgadmin-support |
Hi
On Fri, Jul 7, 2017 at 9:20 AM, Mike Surcouf <mikes(at)surcouf(dot)co(dot)uk> wrote:
> Hi Dave
>
>
>
> 30 second start-up so still very slow for me.
>
That's strange - I get < 12s even on my underpowered virtual machine.
What spec machine are you running? Can you try with AV disabled?
>
>
> Consistently get an exception when closing( see attachment)
>
Also strange. I do not see that. Is there any more info in the event log
etc?
>
>
> Did webpack not make it?
>
> I still get 167 requests on start up.
>
The basic infrastructure is there now, and we've made almost all the JS
code static now so it avoids the templating engine, but there's still work
to do to pack it all.
Thanks.
>
>
> Thanks
>
>
>
> Mike
>
>
>
> *From:* Dave Page [mailto:dpage(at)pgadmin(dot)org]
> *Sent:* 06 July 2017 15:59
> *To:* pgadmin-hackers; pgAdmin Support
> *Subject:* Windows testing required: Updated runtime
>
>
>
> 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
>
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2017-07-07 08:45:34 | Re: Windows testing required: Updated runtime |
Previous Message | Mike Surcouf | 2017-07-07 08:20:46 | RE: Windows testing required: Updated runtime |
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2017-07-07 08:45:34 | Re: Windows testing required: Updated runtime |
Previous Message | Mike Surcouf | 2017-07-07 08:20:46 | RE: Windows testing required: Updated runtime |