| Time |
Nick |
Message |
| 06:38 |
|
rjackson_isl_hom joined #evergreen |
| 07:50 |
|
BDorsey joined #evergreen |
| 08:00 |
|
collum joined #evergreen |
| 08:13 |
|
rfrasur joined #evergreen |
| 08:35 |
|
mmorgan joined #evergreen |
| 08:48 |
|
mantis1 joined #evergreen |
| 08:49 |
|
jvwoolf joined #evergreen |
| 09:29 |
|
rjackson_isl_hom joined #evergreen |
| 10:00 |
berick |
any Simple Reports users out there? curious about other's experinces WRT report run times. quite sluggish here, but it's possible i missed something in my backporting. |
| 10:10 |
miker |
berick: I'm sure there are indexes that could help, and perhaps improvements to the sql to assist PG in planning, and even PG settings that would be good to tweak ... but generally, unless we're talking about days, report runtime isn't usually a primary concern. |
| 10:14 |
berick |
miker: k, yeah, i figure there's some indexes, etc. we could add. as a data point, my last attempt timed out out after 6 hours. |
| 10:14 |
berick |
it was barebones |
| 10:20 |
|
rjackson_isl_hom joined #evergreen |
| 10:21 |
csharp_ |
I'm backporting it here to my 3.8 test server just to play around |
| 10:25 |
miker |
berick: well, barebones is ... relative, if you look at the source query. "less filters" doesn't necessarily mean "less work for PG" |
| 10:26 |
berick |
this one was count of circs per month in 2018 |
| 10:38 |
miker |
I'd suggest SR might be the wrong tool for that particular report ;) ... and that's only about 1/4 snarky -- the example a trivial template to create and share in the normal reporter, and SR is meant to make Hard(tm) things (arguably some impossible things, for normal folks in the normal reporter) simple(r), not all things one-click easy AND fast. It trades internal complexity for external simplicity. |
| 10:39 |
miker |
but there are almost certainly some things that could be tweaked/indexed to keep that particular report from timing out |
| 11:01 |
JBoyer |
It was also used on some relatively large databases (including just outputting all of the possible fields) in psql, though on 9.6. Are you on pg 10 berick ? |
| 11:01 |
berick |
JBoyer: yep, PG 10 on this particular server |
| 11:02 |
JBoyer |
I thought some things got unexpectedly slower from 9.6 to 10, it may be that some tweaks may be needed to get the query parser to cooperate again. |
| 11:04 |
berick |
if there's a report you want me to try, i'm game. |
| 11:06 |
JBoyer |
Your count of circs per month example above would be useful. Just pulling the resulting SQL from logs and running it against explain (and explain analyze if you don't need that db core for a while...) would give some potential leads. |
| 11:19 |
berick |
JBoyer: just the EXPLAIN: https://gist.github.com/berick/f62bc54bd55962e361e3c8aff5469abd |
| 11:19 |
berick |
running analyze now |
| 11:22 |
berick |
it's entirely possible I have some local customization that's bogging things down |
| 11:32 |
|
jihpringle joined #evergreen |
| 11:36 |
pinesol |
News from commits: LP#1771636: Add release notes entry <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=9c52e2e649ef113574c139891c2eacfe5bc76622> |
| 11:44 |
|
eglogbot joined #evergreen |
| 11:44 |
|
Topic for #evergreen is now Welcome to #evergreen (https://evergreen-ils.org). This channel is publicly logged. |
| 12:07 |
jvwoolf |
Trying to figure out if there is a way I can program in a future date into a recurring report (like now() + '3 years'::interval). Anybody know? |
| 12:17 |
berick |
jvwoolf: you mean directly in the database? just one report occurrence or all following occurrences? |
| 12:19 |
csharp_ |
jvwoolf: very curious about the use case - I've never gotten a request like that :-) |
| 12:20 |
csharp_ |
maybe checking for bad circ dates? |
| 12:21 |
jvwoolf |
csharp: Trying to estimate the number of card renewals |
| 12:22 |
JBoyer |
berick, Thanks, did you use the pre-transformed year as a filter or apply the year filter to the timestamp? I'm curious if a Between on the timestamp for the year would be significantly different. (Not that users should have to do that, but it's a data point) |
| 12:22 |
jvwoolf |
We generally do 3 years across the board so I thought anything within the month with an expiration date of 3 years from now was a likely candidate |
| 12:23 |
JBoyer |
jvwoolf++ I've seen that use case also. And it is helpful to find out who's checking items out for 100 years each December. :) |
| 12:24 |
jvwoolf |
berick: Trying to figure out if I can do it in the reporter |
| 12:24 |
berick |
JBoyer: the display field is 'circ start year plus month', the filter is 'circ start time' transformed into year with Equals. |
| 12:25 |
mmorgan |
jvwoolf: So it sounds like you're counting patrons, not circs. |
| 12:25 |
jvwoolf |
Oh and csharp_ ^ |
| 12:25 |
jvwoolf |
mmorgan: Correct |
| 12:26 |
mmorgan |
And looking at edit date and expiration date? |
| 12:26 |
jvwoolf |
Yes exactly |
| 12:26 |
jvwoolf |
I have record creation date in there too to weed out new registrations, but that's easy to accomodate for |
| 12:28 |
jvwoolf |
Last edit date is also easy to accomodate for, it's the expiration date in the future that I'm struggling with. Possible the best I can do is use expiration date transformed to Year + Month with a Greater than operator. |
| 12:30 |
csharp_ |
jvwoolf: ah! |
| 12:31 |
csharp_ |
berick++ |
| 12:32 |
csharp_ |
jvwoolf++ |
| 12:32 |
csharp_ |
TIL you can input future dates in reports - I bet PINES people out there already do that |
| 12:33 |
csharp_ |
I'm kind of stuck on date ranges (between), so I sometimes forget about the utility of Year+Month |
| 12:33 |
jvwoolf |
csharp_: Ironically, I learned that trick from you! |
| 12:33 |
csharp_ |
figures :-) |
| 12:34 |
* csharp_ |
can't remember things one day to another |
| 12:34 |
jvwoolf |
I'm also stuck on date ranges but trying to make these changes for recurring report templates where I can |
| 12:34 |
* csharp_ |
fights with 3.8 vs 3.9 angular |
| 12:35 |
csharp_ |
may just need to fully upgrade to 3.9, but since that involves a lot of git work to merge in PINES customizations I was trying not to |
| 12:36 |
csharp_ |
also, the PINES customizations in question might be the problem |
| 12:51 |
|
jihpringle joined #evergreen |
| 13:40 |
|
CCLD_IT joined #evergreen |
| 13:42 |
|
jihpringle joined #evergreen |
| 13:44 |
CCLD_IT |
Hello everyone, hopefully a quick ?.... I am replacing a self-check station running CheckEze, it says sorry no response from the library computer. When CheckEze first starts, it says not registered by the device name? Do we have an onsite sip server to authenticate these requests? |
| 13:54 |
rhamby |
CCLD_IT welcome! This is a community Evergreen channel. For specific implemenation like SIP2 server setup you would need to contact whoever is hosting you. |
| 13:56 |
csharp_ |
CCLD_IT: could be a firewall between the client and the SIP2 server - also an Evergreen account needs to exist for the client to use for logging in |
| 13:56 |
csharp_ |
and that client credential needs to be added to a file on the SIP2 server |
| 14:14 |
CCLD_IT |
Thank you! |
| 14:20 |
|
jvwoolf left #evergreen |
| 14:27 |
|
rjackson_isl_hom joined #evergreen |
| 15:27 |
|
rjackson_isl_hom joined #evergreen |
| 15:31 |
mmorgan |
FIFO question. If a library has FIFO set as best-hold selection sort order, shouldn't the item be captured for the hold with the highest priority, no matter the pickup location? |
| 15:32 |
mmorgan |
I'm finding that a local hold is captured when there are higher priority holds for pickup elsewhere. |
| 15:33 |
mmorgan |
We don't use FIFO, just testing for a particular situation. |
| 17:04 |
|
mmorgan left #evergreen |
