saving the etherpad which we have worked with during the Varnish Developer Day 3rd quarter 2018 (VDD18Q3) for later reference

original URL https://etherpad.wikimedia.org/p/vdd2018q3

edit: reformat only

VDD 2018Q3 Hamburg

Bi-annual release strategy

• works well, keep it
• review website, communicate more clearly

R6.1 post-mortem

• pro
  • code freeze-ish (feature freeze)
  • continue making autumn releases boring
• con
  • (nil)

March '19 release wishlist

• VDP list
• Backends/directors and all that...
• 6.2 or 7.0 ? -- decide around Xmas
• Python3
• vmod.tell
• vtest::for {var} in {list} {...}
• VCL variables / objects
• restricting VMOD functions to specific methods

Release doc simplification:

Updating

• What does upgrading to this release entail ?
• Decision support to upgrade or not -> reused as top part of homepage/release/X.Y.Z

Changes

• High-level description of changes
• Sorted in "Admin, VCL-writer, VMOD writer" sections

Announcement

• homepage
• announce@varnish-cache.org
• announce upcoming release & features 4-6 weeks ahead

changes.rst (outside sphinx)

• keep as reference for internals

Varnishtest divorce

• Export vtest from varnish-cache tree ?
• Import vtest to varnish-cache from vtest tree ?
• Scope:
  • 88 source files, 28977 lines
  • 41 test cases (a*.vtc)
• vtest tree: build with/without vtc_varnish
• decision: git submodule
• vtest project is source only on github
• simple Makefile builds vtest binary, no autocrap

Benchmark testing

I (phk) have no feeling with our performance right now... ... but some of us are having an eye on it

-> review the amount of logging - check what can be removed / hidden behind vsl mask

Vtest

• Where is linux ? Pål Hermunn will pick this up and try to convince someone (TM) to contribute this.

Backends

• Global backends / VCL backends / VMOD backends

• pointer to VCL-lifetime factories, not instantiating before asked

• criteria

  • no lock per task

  • no overhead on cache hit

     /* inofficial slink notes */
     struct muffin {
      (void *)func(enum type, struct muffin *)  *bake;
      void                                      *ptr;
      (void)func(void *)                        *eat;
    };

VDP restructure patch

https://github.com/varnishcache/varnish-cache/pull/2673

1. function pointers
2. error handling
3. last flag
4. VDP list

Martin to make a new split patch set

stats/mailbox

problem is:

stat += 0; // under stats lock

stat += i; // elsewhere

• add "group" to .vsc file
• sort struct in groups
• json still same order
• sub-structs per group
• sum-function per group
  • solves above
• timeout for summing
• @phk

vtim? -> integers ?

• annotate with typedefs vtim_mono vtim_real
• 64bit with 1/4th 1/8th microsecond resolution as basis for alternative impl.
• printf macros for fmt string & argument printf("valasksdfs" VTIMFMT "sdfsfsd", VTIMARG(t0));
• simple benchmark to get a feeling
• @slink

Quic?

(not discussed)