ID |
Date |
Author |
Topic |
Subject |
Text |
|
1668
|
28 Aug 2019 |
lcp | Forum | History plot problems for frontend with multiple indicies | hi,
> > That makes things more
|
|
1669
|
29 Aug 2019 |
Ben Smith | Forum | History plot problems for frontend with multiple indicies | Hi Nick,
I confirm that this issue appears when using |
|
Draft
|
29 Aug 2019 |
Nick Hastings | Forum | History plot problems for frontend with multiple indicies | Hi LCP,
thanks for the suggestion and link. Unfortunatly |
|
Draft
|
29 Aug 2019 |
Nick Hastings | Forum | History plot problems for frontend with multiple indicies | Hi Ben,
thanks for your reply. I can confirm that |
|
1672
|
01 Sep 2019 |
Nick Hastings | Forum | History plot problems for frontend with multiple indicies | Hi Ben,
thanks for your reply. I can confirm that |
|
1689
|
16 Sep 2019 |
Konstantin Olchanski | Forum | History plot problems for frontend with multiple indicies | > My first question would be why are you using
several font-ends at all? That makes things
more
|
|
1691
|
16 Sep 2019 |
Konstantin Olchanski | Forum | History plot problems for frontend with multiple indicies | > it's probably better to run a multi-threaded
setup, than individual frontends.
|
|
1692
|
16 Sep 2019 |
Konstantin Olchanski | Forum | History plot problems for frontend with multiple indicies | > thanks for your reply. I can confirm that
your suggested workaround does indeed
> make the problem dissapear.
|
|
1693
|
16 Sep 2019 |
Nick Hastings | Forum | History plot problems for frontend with multiple indicies | Hi Konstantin,
thanks for your reply.
|
|
1696
|
17 Sep 2019 |
Konstantin Olchanski | Forum | History plot problems for frontend with multiple indicies | > [local:e666:S]History>ls -l /History/Events
> Key name Type
#Val Size Last Opn Mode Value
|
|
Draft
|
18 Sep 2019 |
Nick Hastings | Forum | History plot problems for frontend with multiple indicies | > > [local:e666:S]History>ls -l /History/Events
> > Key name Type
#Val Size Last Opn Mode Value |
|
1699
|
18 Sep 2019 |
Nick Hastings | Forum | History plot problems for frontend with multiple indicies | Hi Konstantin,
> > [local:e666:S]History>ls -l /History/Events
|
|
1710
|
27 Sep 2019 |
Konstantin Olchanski | Forum | History plot problems for frontend with multiple indicies | We should fix this for midas-2019-10.
https://bitbucket.org/tmidas/midas/issues/193/confusion-in-history-event-ids
|
|
1986
|
24 Aug 2020 |
Konstantin Olchanski | Forum | History plot problems for frontend with multiple indicies | This turned out to be a tricky problem. I
am adding a warning about it in mlogger.
This should go into midas-
|
|
2015
|
19 Nov 2020 |
Joseph McKenna | Forum | History plot consuming too much memory |
A user reported an issue that if they were |
|
2016
|
19 Nov 2020 |
Stefan Ritt | Forum | History plot consuming too much memory | The history code is right now programmes in
such a way that when you request
an old time window, then all data from that |
|
2017
|
20 Nov 2020 |
Joseph McKenna | Forum | History plot consuming too much memory | Poking at the behavior of this, its fairly
clear the slow response is from the data
|
|
2018
|
20 Nov 2020 |
Stefan Ritt | Forum | History plot consuming too much memory | > Taking this down a tangent, I have a mild
concern that a user could temporarily
> flood our gigabit network if we do have |
|
2028
|
27 Nov 2020 |
Konstantin Olchanski | Forum | History plot consuming too much memory | >
> Tested with midas-2020-08-a up until the
HEAD of develop
|
|
2029
|
27 Nov 2020 |
Konstantin Olchanski | Forum | History plot consuming too much memory | >
> With the current code, we are limited to
loading history data up to 50% of
|
|