Ever used a database? Wondered where it magically puts all your data? Wondered what "transactions" are and exactly why we need them? Heard some very technical-looking folk talking about "ACID"? Then this is the talk for you.
In this demo-documentary of a single byte, of the life-cycle of a single byte from birth to death, we attempt to demystify the internals of a relational databases' storage mechanism using PostgreSQL as an example.
In some use-cases, Redis can double its memory use during a snapshot operation (replicas attaching, periodically for backups, rewriting AOF, as requested for backups, ...), generally requiring substantial "copy on write" overhead for heavy write loads, up to 100% in some cases. We demonstrate a technology that reduces this memory usage to .3-.5%, or roughly 1/200 the overhead of existing Redis snapshots, while seeing little difference in throughput or latency.
"I'm sure if I work hard, my contribution will one day be recognized and I'll get a raise." --Everyone At Some Point In Our Careers
The world is unfair; this talk won't do much to fix that-- but it will give insight from two industry veterans on how to maneuver within the world we currently inhabit.
RISC-V is a Free and Open RISC Instruction Set Architecture provided under BSD license, unleashing new means of processor innovation with open collaboration, delivering a new freedom of hardware and software design. It's filled with the potential to do what Linux started for the software ecosystem, some 25 years ago, i.e., lighting the open source movement, but for hardware and CPU design and influencing CPU innovation for rest of the 21st Century and beyond. We will talk about the RISC-V ecosystem, and the progress it has made thus far in a short span, from 2010 onwards.
Many organizations are using open source software without purposeful governance in place. These organizations need to establish processes and practices to govern the way in which they consume and contribute.
F Prime, developed at NASA’s Jet Propulsion Laboratory has been used to control cubesats, instruments, and other spaceborne systems at NASA. This talk will walk through the basics of F Prime, its architecture, and how it is used to develop embedded flight software. Attendees should expect to leave with an understanding of how F Prime can be used to further their own embedded software projects both in space and on Earth.
- How HTTP flood may make you HTTP parser the bottle neck
- x86-64 and branch mispredictions, caching, unaligned memory access
- C compiler optimizations for multi-branch statements and autovectorization
- switch-driven FSM versus direct jumps
- what makes HTTP strings special and why LIBC isn't good
- strspn() and strcasecmp() algorithms for HTTP strings using SSE and AVX
- efficient custom filtering to prevent injection attacks
- the cost of FPU context switch and how the Linux kernel works with SIMD
I will explain the background of fight, flight, and freeze, and how it applies to organizations. I will give examples and suggestions on how to identify your own organizational trauma and how to help heal it.
Many businesses need to have tighter controls over some of their big data, but the data needs to be stored with less sensitive data. File systems allow protections to be given at the file level, but not finer grain than that. By modifying the Apache ORC columnar file format, we are adding column encryption so that specific columns can be encrypted. This allows your personally identifiable information (PII) to be encrypted while the majority of your data is not.
There are many Security Frameworks to choose from: NIST, CIS, ISO, PCI, but only PCI is prescriptive in its controls. So if you are trying to start or measure your current security practices the PCI is a good framework to use. Because it is is prescriptive it is well understood how to meet the controls and it tells you what you need to put in place to pass the control test. But even then the PCI is hard to grasp for many because it is large and they don’t understand why a control was created. There is no “Why” answered in the control definition. In my presentation I try to answer, “Why"