2020-08-03 kdb+ Project Meeting Minutes

Meeting minutes status: Draft (pending approval)

Table of Contents

Date/Time

  • August 3rd, 2020. 10am ET

Attendees

NameOrganisationGithub ID 
Rob UnderwoodFINOSbrooklynrob
Morgan Stanleyalvin-c-shih
Aaron DaviesMorgan Stanleyadavies42
FINOSmcleo-d
Jonny PressAquaQ Analyticsjonnypress
Peter GyorokMorgan Stanleygyorokpeter
Tim BeletskiyJP Morgan
Gary DaviesAquaQ Analyticsdrgdavies




Agenda

TimeItemWhoNotes from the Meeting
5 minConvene & roll call.

All


5 minReview and approve minutes from last meeting.All
  • Found some additional notes from last meeting.
    • Will update and have the vote at the September call.
5 min

"Studio for kdb+" updates.

  • Features in the pipeline?
  • Icon status?
  • FYI: May be viable to incorporate Creative Commons-licensed materials into FINOS projects.
    • FINOS will look at it more closely when the need arises.
All
  • Icon designer on vacation.
    • Some internal review / tweaking to take place.
    • Will be released shortly after that.
5 min

FINOS Open Developer Platform.

  • Might as well go with minutes in it since it's the way forward.
  • Can try to convert non-minutes Wiki content to Markdown with Pandoc.
  • Curious about manual override of Attendee List in case:
    • banks block login to GitHub unless named on the CCLA
    • attendees lazy / paranoid about persistent login to GitHub
All
25 min

MemVerge vs qclone.

  • "AquaQuarantine: MemVerge and kdb+" video suggested use cases where MemVerge might be used in a kdb+ plant.
  • Shared memory pages sounds like something qclone can do for free without exotic hardware.
  • Tease apart the use cases and see if they're interesting enough to put out the qclone plugin and cooperatively develop wrapper functions to support agreed-upon use cases.
  • For cases that qclone doesn't work, investigate alternatives such as:
All
  • Use cases that attendees found interesting:
    • Debugging complex memory state with high computation.
    • EOD save down.
    • Snapshot to a file or across a network.
    • Worker processes for heavy compute like feature engineering.
  • qclone limitations:
    • Doesn't offer any resilience in the face of host crash.
  • Questions:
    • Process management for clones?
    • Containerization?
  • Will try to get qclone PoC released for experimentation.


5 minAOBAll

Action Items




Need help? Email help@finos.org we'll get back to you.

Content on this page is licensed under the CC BY 4.0 license.
Code on this page is licensed under the Apache 2.0 license.