| Time |
Nick |
Message |
| 06:01 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 07:30 |
|
rjackson_isl_hom joined #evergreen |
| 07:56 |
|
mantis joined #evergreen |
| 08:42 |
|
mmorgan joined #evergreen |
| 08:56 |
|
Dyrcona joined #evergreen |
| 09:02 |
|
rfrasur joined #evergreen |
| 09:20 |
|
jvwoolf joined #evergreen |
| 10:23 |
|
jvwoolf joined #evergreen |
| 10:44 |
|
jvwoolf joined #evergreen |
| 10:56 |
|
jvwoolf left #evergreen |
| 11:00 |
|
jvwoolf joined #evergreen |
| 11:12 |
Dyrcona |
I have started a load of 12,567 records with located URIs with pl_profiler enabled on Pg 10. I'll repeat this load on Pg 11 through 13 in the coming days. |
| 11:18 |
mmorgan |
Dyrcona: I'm interested in your results. Do you know how many URIs are in each record or does it vary? |
| 11:19 |
Dyrcona |
mmorgan: It's usually 1 in the incoming file, but some have 2. The majority of records, over 10,000, match existing records so the number of URIs varies. |
| 11:20 |
Dyrcona |
I've loaded this set of records into production already, which is why I'm using a dump from July 11 for this test. |
| 11:23 |
* mmorgan |
nods. We've been looking at how long it takes to load each record and have found a record with 10 links take on average 12 seconds. |
| 11:23 |
Dyrcona |
I suspect that Pg 10 will give the best results, and I'm doing it as a benchmark. Also, Pg 10 is currently optimized on this server. |
| 11:23 |
Dyrcona |
mmorgan: It gets slower on newer Pg versions, and I want to find out where/why so we can fix it. |
| 11:24 |
mmorgan |
Dyrcona++ |
| 11:25 |
Dyrcona |
When testing a timed version of this script, I've seen it take well over 20 seconds to update some records |
| 11:25 |
|
jvwoolf joined #evergreen |
| 11:26 |
Dyrcona |
I usually kill it after a few days on Pg 12. :( |
| 11:26 |
mmorgan |
:-( |
| 11:27 |
Dyrcona |
I'm using the "same" script that I use in production, though I've stripped out all the logging and timing code and replaced it with the database calls to start and end the profiler. |
| 11:38 |
Dyrcona |
Hmm. I should add code to the script to generate the report and reset the statistics when it ends.... Think I'll add that for the later runs. |
| 12:02 |
|
jihpringle joined #evergreen |
| 12:13 |
|
mmorgan1 joined #evergreen |
| 12:50 |
|
jvwoolf joined #evergreen |
| 13:00 |
dluch |
Reminder that DIG is meeting in an hour, on Zoom this month. Connection info and agenda are here: https://wiki.evergreen-ils.org/doku.php?id=evergreen-docs:dig_meetings:20210805-agenda |
| 13:47 |
|
alynn26_away joined #evergreen |
| 14:14 |
|
jvwoolf left #evergreen |
| 14:40 |
|
nfBurton joined #evergreen |
| 16:09 |
|
mmorgan joined #evergreen |
| 16:31 |
|
troy joined #evergreen |
| 16:47 |
|
jihpringle joined #evergreen |
| 16:55 |
|
sandbergja joined #evergreen |
| 16:57 |
sandbergja |
I am working on getting credit card payments set up with the campus AuthorizeNet subscription. The business office is asking me if Evergreen is able to authorize then capture a transaction? Or if it just can authorize and then they have to manually capture? |
| 17:10 |
|
mmorgan1 joined #evergreen |
| 17:10 |
|
mmorgan1 left #evergreen |
| 17:33 |
|
jihpringle joined #evergreen |
| 17:34 |
Bmagic |
anyone have any clues as to how I can have an auto-renew trigger fire and complete with no errors but not actually renew the circulation? user_data contains no data but the action_trigger.event row exists and looks healthy otherwise |
| 17:38 |
|
nfBurton joined #evergreen |
| 17:45 |
Bmagic |
oh, it looks like the reason comes out in the subsequent email trigger event. Unless you have the followup email to the patron, it doesn't look like we can tell (from the database) why something doesn't get auto-renewed? |
| 17:49 |
|
jihpringle joined #evergreen |
| 18:01 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
