lumosql.20220304.1300 Minutes

Meeting started by danshearer1 at 2022-03-04 11:57:43+0000 (full logs).

Meeting Summary

1. Prologue (danshearer1, 11:57:43)
   1. MEETING_NAME: lumosql.20220304.1300 (danshearer1, 11:58:56)
   2. ATTENDEE: Claudio (Labhraich, 11:59:03)
   3. ATTENDEE: danshearer1 (danshearer1, 11:59:12)
   4. ATTENDEE: Björn (BKJ621, 11:59:13)
   5. ATTENDEE: gabby_bch (gabby_bch, 12:00:23)
2. Introductory stuff (danshearer1, 12:01:11)
   1. INFO: Ruben is driving and therefore not here. But he posted notes earlier (danshearer1, 12:01:33)
   2. INFO: Ruben will commit his bibliographic data to doc/references later (danshearer1, 12:02:53)
   3. INFO: Ruben's summary is " ABE is not ready for the feature set we want to support. My next goal with this document is to find out which subsets of the feature set we can support" (danshearer1, 12:03:04)
3. Brussels Meetup (danshearer1, 12:05:34)
   1. INFO: Björn has sent an email with details. We need to agree and then do the actions. (danshearer1, 12:06:02)
   2. ACCEPTED: We meet in Brussels, arriving at latest on Sunday 3 April and leaving earliest Thursday 7 April (danshearer1, 12:16:59)
   3. ACCEPTED: We book however we want and then tell Björn (a) the dates so he can book rooms and (b) tickets so he can handle reimbursements (danshearer1, 12:20:21)
   4. ACTION: Dan to confirm to VUB about room requirements as soon as we know. Certainly one lab as promised and one good sized presentation space. (danshearer1, 12:26:07)
   5. ACTION: danshearer1 to work on talk abstracts, and checking VUB can host 6th April, and then advertise (danshearer1, 12:42:21)
4. Next steps in docs/benchmarking (danshearer1, 12:47:22)
   1. INFO: We have increased the combined dataset a bit, but more is needed (danshearer1, 12:47:45)
   2. ACTION: danshearer1 to submit a large cluster run asap (danshearer1, 12:47:59)
   3. INFO: Gabby has got an R Shiny server working. (danshearer1, 12:48:34)
   4. ACTION: gabby_bch to finish graphs to the point where we can compare performance of all SQLite vs SQLite, and all LMDB vs LMDB, in addition to what we currently have (danshearer1, 12:50:01)
   5. ACTION: gabby_bch fill in the gaps in the combined bechmark database (gabby_bch, 12:52:49)
   6. ACTION: Labhraich to investigate next step for adding CPU and DISK to older benchmarks, Dan providing data for his runs (danshearer1, 12:58:29)
   7. ACTION: danshearer1 to incorporate better data, more data and better graphs into a new version of the benchmarking release doc, which can then be committed to the repo (danshearer1, 13:00:08)
5. LumoSQL internals and next steps (danshearer1, 13:03:05)
   1. INFO: Labhraich is continuing to work on a general mechanism for adding data to SQLite databases so that unmodified SQLite does not notice (danshearer1, 13:05:08)
   2. INFO: This can be seen as adding internal structure/data models to rows and tables that has never existed before. (danshearer1, 13:06:15)
   3. INFO: Labhraich wants to be able to store metadata about blobs in SQLite databases (danshearer1, 13:07:47)
   4. INFO: Ruben is working on ways to implement blobs that have different levels of data access and control, as well as integrity and uniqueness (danshearer1, 13:08:01)
   5. INFO: Ruben is about Lumions, whereas Claudio is about implementing either Lumions or some other scheme (danshearer1, 13:08:57)
   6. INFO: Dan has received helpful feedback about the LMDB backend and alternative source trees, and is following that up. This was in response to the Benchmarking 0.6 document. (danshearer1, 13:09:30)
   7. ACTION: Dan to poke the people who recieved 0.6 as soon as we have slightly better data that shows more obviously the ups and downs in SQLite and LMDB. (danshearer1, 13:10:28)

Meeting ended at 2022-03-04 13:22:51+0000 (full logs).

Attendees

1. BKJ621 (aka Björn) - 24 lines
2. Labhraich (aka Claudio) - 43 lines
3. danshearer1 - 110 lines
4. gabby_bch - 8 lines
5. lumosql-meetbot - 5 lines

Action Items

1. Dan to confirm to VUB about room requirements as soon as we know. Certainly one lab as promised and one good sized presentation space.
2. danshearer1 to work on talk abstracts, and checking VUB can host 6th April, and then advertise
3. danshearer1 to submit a large cluster run asap
4. gabby_bch to finish graphs to the point where we can compare performance of all SQLite vs SQLite, and all LMDB vs LMDB, in addition to what we currently have
5. gabby_bch fill in the gaps in the combined bechmark database
6. Labhraich to investigate next step for adding CPU and DISK to older benchmarks, Dan providing data for his runs
7. danshearer1 to incorporate better data, more data and better graphs into a new version of the benchmarking release doc, which can then be committed to the repo
8. Dan to poke the people who recieved 0.6 as soon as we have slightly better data that shows more obviously the ups and downs in SQLite and LMDB.

Action Items by Attendee

• Labhraich
  1. Labhraich to investigate next step for adding CPU and DISK to older benchmarks, Dan providing data for his runs
• danshearer1
  1. danshearer1 to work on talk abstracts, and checking VUB can host 6th April, and then advertise
  2. danshearer1 to submit a large cluster run asap
  3. danshearer1 to incorporate better data, more data and better graphs into a new version of the benchmarking release doc, which can then be committed to the repo
• gabby_bch
  1. gabby_bch to finish graphs to the point where we can compare performance of all SQLite vs SQLite, and all LMDB vs LMDB, in addition to what we currently have
  2. gabby_bch fill in the gaps in the combined bechmark database

Generated by HCoop Meetbot v0.4.1 (15 Nov 2021)