From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Dominik Csapak <d.csapak@proxmox.com>,
Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox-backup 2/2] ui: tape: increase tapestore interval
Date: Wed, 10 Mar 2021 13:41:41 +0100 [thread overview]
Message-ID: <0814baf1-ab66-a67a-cee0-453072e844cb@proxmox.com> (raw)
In-Reply-To: <8b5efacb-163f-8e1a-4b37-bf640a8fd031@proxmox.com>
On 10.03.21 13:32, Dominik Csapak wrote:
> On 3/10/21 12:47 PM, Thomas Lamprecht wrote:
>> On 10.03.21 12:38, Dominik Csapak wrote:
>>>
>>>
>>> On 3/10/21 12:19 PM, Thomas Lamprecht wrote:
>>>> On 10.03.21 10:10, Dominik Csapak wrote:
>>>>> from 2 to 60 seconds. To retain the response time of the gui
>>>>> when adding/editing/removing, trigger a manual reload on these actions
>>>>>
>>>>> Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
>>>>
>>>> Please add my Suggested-by or Reported-by tags for reference the next time,
>>>> thanks!
>>>>
>>>
>>> yes of course, sorry
>>
>> Thanks!
>>
>> btw. can you please freshen up my brain on the storeid config from UpdateStore?
>> As its not used there directly and it's base class Ext.data.Store only knows
>> about storeId [0] (note the casing difference), and using that one would actually
>> register the store to the Ext.data.StoreManager [1] and we could avoid the detour
>> over querying the nav tree but do a
>>
>> Ext.data.StoreManager.lookup('pbs-tape-drive-list').load();
>>
>> instead. Not sure about any extra cost of that manager, but code wise it would
>> be quite less (and only called from places where we know that PBS.enableTapeUI
>> is true already).
>>
>> And if the UpdateStores `storeid` property is only a "copy-is-my-hobby" left
>> over, or really misspelled then I'd maybe drop it or fix spelling, respectively.
>>
>> [0]: https://docs.sencha.com/extjs/6.0.1/classic/Ext.data.Store.html#cfg-storeId
>> [1]: https://docs.sencha.com/extjs/6.0.1/classic/Ext.data.StoreManager.html
>
> mhmm after taking a short look at it, we require 'storeid' in the UpdateStore, otherwise it fails with an exception. But i cannot find
> any actual use for that, so i assume it was meant to be storeId in the
> first place but we never noticed
yeah so same findings I had.
>
> i'll check if changing it to storeId has any negative side-effects
> (such as leftover stores after some panel gets destroyed) and would
> send patches to change all occurrences to storeId
>
> if it's too costly (or has other issues) i'd prepare patches to
> drop it from the UpdateStore altogether (since we do not
> seem to use it)
Thanks!
next prev parent reply other threads:[~2021-03-10 12:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 9:10 [pbs-devel] [PATCH proxmox-backup 1/2] ui: NavigationTree: do not modify list while iterating Dominik Csapak
2021-03-10 9:10 ` [pbs-devel] [PATCH proxmox-backup 2/2] ui: tape: increase tapestore interval Dominik Csapak
2021-03-10 11:19 ` Thomas Lamprecht
2021-03-10 11:38 ` Dominik Csapak
2021-03-10 11:47 ` Thomas Lamprecht
2021-03-10 12:32 ` Dominik Csapak
2021-03-10 12:41 ` Thomas Lamprecht [this message]
2021-03-10 10:01 ` [pbs-devel] applied: [PATCH proxmox-backup 1/2] ui: NavigationTree: do not modify list while iterating Dietmar Maurer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0814baf1-ab66-a67a-cee0-453072e844cb@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=d.csapak@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox