Attendee Survey: MariaDB Server Fest New York 2020 Please enable JavaScript in your browser to complete this form.Who are you?Country:Company:Time zone: How many hours away are you from New York? *East of New York, by 1 hours or moreNew York time zone (Eastern)West of NY, by 1 hour (Central)West of NY, by 2 hours (Mountain)West of NY, by 3 hours (Pacific)West of NY, by 4 hours or moreWould you classify yourself primarily as a: *DBAdevopdevelopermanagerotherPlease write your job position: *How did you follow the Fest?How did you follow fest? *I followed the live New York stream, as it happenedI followed the live New York stream, but slightly late (0-3 hours)I followed the live New York stream, 3 hours or more laterI didn’t follow the fest, just looked at different videos afterwardsYour opinion of the Fest and its format 😀 = Great, 🙂 = Good, 😐 = Average, 🙁 = Bad, 😡 = Terrible, — = No opinion/not applicableContent of presentations: *😀🙂😐🙁😡—Choice and spread of topics: *😀🙂😐🙁😡—Having pre-recorded talks: *😀🙂😐🙁😡—Technical delivery of pre-recorded talks, video editing: *😀🙂😐🙁😡—Duration of most talks being 25 minutes: *😀🙂😐🙁😡—The Q&A session concept: *😀🙂😐🙁😡—Subtitles being provided for the talks: *😀🙂😐🙁😡—Chatting with presenter and attendees over Zulip: *😀🙂😐🙁😡—Having the event in three different timezones, during day-time: *😀🙂😐🙁😡—Duration – three short days, rather than two long days: *😀🙂😐🙁😡—Lack of coffee breaks (pressing Stop/Play was fine by me!): *😀🙂😐🙁😡—Your opinion of our future plans and ideas 😀 = Great, 🙂 = Good, 😐 = Average, 🙁 = Bad, 😡 = Terrible, — = No opinion/not applicableStreaming the Fest also on Facebook: *😀🙂😐🙁😡—Providing tutorials: *😀🙂😐🙁😡—Providing iCal links to presentations: *😀🙂😐🙁😡—Providing Birds-of-a-Feather type Zoom rooms for attendees: *😀🙂😐🙁😡—How often should we do Server Fests?How often should we do Server Fests? *Every 6 monthsEvery 12 monthsNo opinionYour opinion on the presentationsTuesdaySupermetrics and the many bears: a modern day fable on the search for the perfect database: *😀🙂😐🙁😡—Comparing ecosystems: MariaDB and Public Code *😀🙂😐🙁😡—MariaDB meets solid-state computational storage drives: higher performance at lower cost: *😀🙂😐🙁😡—Temporal tables: *😀🙂😐🙁😡—ANALYZE for statements: MariaDB’s hidden gem: *😀🙂😐🙁😡—MariaDB 10.5 new features for troubleshooting: *😀🙂😐🙁😡—Dynamic tracing of MariaDB Server on Linux – problems and solutions: *😀🙂😐🙁😡—MyTile: a cloud-native storage engine based on TileDB: *😀🙂😐🙁😡—WednesdayMySQL 8 vs MariaDB 10.5: *😀🙂😐🙁😡— Modern solutions for modern database load: improvements in the latest MariaDB versions: *😀🙂😐🙁😡—How to migrate from MySQL to MariaDB without tears: *😀🙂😐🙁😡—sql_mode=ludicrous: *😀🙂😐🙁😡—Optimizer Trace walkthrough: *😀🙂😐🙁😡—Introduction to MariaDB Galera Cluster: *😀🙂😐🙁😡—Galera Clustering in MariaDB 10.5 and beyond: *😀🙂😐🙁😡—MariaDB SkySQL: next generation DBaaS from the source: *😀🙂😐🙁😡—ThursdayScalability improvements in MariaDB’s InnoDB storage engine: *😀🙂😐🙁😡—MariaDB on ARM: *😀🙂😐🙁😡—10.5 and beyond: *😀🙂😐🙁😡—AutoML in MariaDB: train and query machine learning models straight from MariaDB: *😀🙂😐🙁😡—Bringing MariaDB closer to the data science community – the MariaDB Jupyter kernel: *😀🙂😐🙁😡—AMA with Monty: *😀🙂😐🙁😡—Building a relational data lake with MariaDB ColumnStore: *😀🙂😐🙁😡—Migration tales: *😀🙂😐🙁😡—It’s all about you: innovation that matters: *😀🙂😐🙁😡—Other feedback:Prove you are human: * = CommentSubmit