Skip to content
View samixyzdev's full-sized avatar
🎯
Focusing
🎯
Focusing

Block or report samixyzdev

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
samixyzdev/README.md

Database execution on specialized hardware

Database systems · computer architecture · specialized hardware

I study how database execution changes when the compute substrate is specialized hardware. My current investigation explores analytical query execution on emerging accelerator platforms.

I am an undergraduate at the University of Michigan studying Computer Science and Mathematical Sciences, with a minor in Electrical Engineering.

Current investigation · Systems evidence · Research

Current investigation

Question. How should analytical operators, data layouts, and memory movement change when the execution substrate is a specialized accelerator?

What I am investigating. I study how database operators can be lowered into accelerator-native kernels, then examine tiling, layout, data movement, and execution behavior.

Evidence. Correctness checks, operator-level benchmarks, layout experiments, and hardware-aware execution traces.

Status. Active faculty-supervised systems research. Research code and unpublished measurements remain private while the work is in progress.

Methods. Python · SQL · Accelerator programming · Systems profiling

Clocked wavefront observatory

This conceptual output-stationary trace follows one complete 3×3 matrix multiplication. Blue A packets move right, amber B packets move down, and a white phase-lock ring appears only when an operand pair meets at a crosspoint. Each node locks three accumulator arcs before its teal output contact closes.

The active MAC envelope is 1 · 3 · 6 · 7 · 6 · 3 · 1; nine outputs become ready in an anti-diagonal 1 · 2 · 3 · 2 · 1 wave. In total, the trace records 27 MAC events and 9 completed C values.

Animated conceptual cycle trace of a 3 by 3 output-stationary MXU: blue A packets and amber B packets meet at circular crosspoints, three accumulator arcs lock per node, and teal output contacts close diagonally

Conceptual cycle trace — not a physical accelerator floorplan.

Execution path

The broader project is an iterative systems investigation, not a fixed linear pipeline. Measurements feed back into operator lowering, tiling, and layout.

Static systems cross-section connecting a relational operator to an accelerator-native execution plan, memory movement and an accelerator substrate, then feeding correctness, latency, and bandwidth measurements back into layout and kernel decisions

Selected systems evidence

Two-way superscalar processor

Question. How much instruction-level parallelism can a compact pipeline extract while keeping hazards and forwarding understandable?

Built. A two-wide LC2K core with micro-op lowering, an eight-entry micro-op queue, a four-entry windowed issue engine, dual ALUs, one load/store-capable lane, and explicit writeback bypass paths.

Animated RTL-derived trace of a two-wide LC2K core: two loads split into address and memory micro-ops, noncontiguous address micro-ops issue together, a load holds the issue packet while memory responds, and r2 forwards from writeback into an ADD producing r3 equals 11

Cycle-accurate playback from an RTL simulation of simple_add; short color rails identify instructions that entered decode together, while token outlines identify operation type. The initial I-cache fill is omitted and animation time is slowed for inspection. Topology is schematic, not a physical floorplan.

Evidence. Cycle-accurate memory-trace verification and gate-level synthesis under a 20 ns clock constraint.

Status. Completed course project; implementation is private.

Methods. SystemVerilog · VCS · Verdi · Synopsys Design Compiler

Operating systems and concurrency

Question. Which invariants keep concurrent runtimes, network services, and virtual memory correct under interleaving and failure?

Built. A preemptive user-level thread library, a concurrent TCP file server with hand-over-hand read-write locking and crash-consistent updates, and a virtual memory manager with Clock replacement and copy-on-write fork.

Evidence. Adversarial concurrency tests, protocol validation, fault-path testing, and correctness traces.

Status. Completed systems coursework; implementations are private.

Methods. C++ · Linux · Threads · TCP · Virtual memory

Language-model components from first principles

Question. What is hidden behind the high-level interfaces of a Transformer implementation?

Built. BPE training and tokenization, embeddings, RMSNorm, SwiGLU, scaled dot-product attention, multi-head self-attention, RoPE, and Transformer blocks with reference-output tests.

Evidence. Coursework repository and visible implementation scope.

Status. Supporting coursework, not a current research focus.

Methods. Python · PyTorch · Transformers

Research and publication

I co-authored PANCDetect: Early Detection of Pancreatic Cancer from Multimodal EHR Data with LLM Embeddings, a preprint for which I contributed to clinical data preprocessing and analysis.

Methods and contact

I work across operator semantics, systems implementation, profiling, benchmarking, memory-layout analysis, and accelerator kernels. The easiest way to reach me is through LinkedIn or email.

Pinned Loading

  1. A_language_model_from_scratch A_language_model_from_scratch Public

    Forked from stanford-cs336/assignment1-basics

    Student version of Assignment 1 for Stanford CS336 - Language Modeling From Scratch

    Python