









6,000 plants growing in our 8,600 sq ft grow. we have (12) 4’x90’ beds and are pushing 1.2 plants per square foot.
Year number 5 with 25 turns in the same KIS living soil!
Hi everyone,
Found my way here after seeing Nicholas Walker’s post on LinkedIn. Been lurking for a bit and figured I should introduce myself.
I’m Henrique, a commercial grower from Portugal. I run PREZE, a licensed medicinal facility where we’re currently growing three cultivars for the European market in around 2,400 m² of glass greenhouse.
We’re running Fluence RAPTR LEDs, hanging gutters, heating and a custom HVAC/dehumidification setup.
We’ve only been operational for about 6 months, so we’re still learning a lot and dialing things in, but I’m pretty happy with where the flower is heading.
This is one of our current batches — Funk Bomb, 22% THC, destined for the German medicinal market.
I mainly joined because there seem to be quite a few people here operating at commercial scale and dealing with the same problems we are.
We definitely don’t have everything figured out. Climate control, irrigation strategy, airflow, disease pressure, post-harvest, scaling SOPs… plenty of things have already given us headaches.
Happy to share what has worked, what hasn’t, some of the mistakes we’ve made, and compare notes with other growers here.
Looking forward to contributing.
We are seeing crazy results from the lights and think the far red is really doing it
HeadPeace = (Tiger's Milk x Snow Lotus) x Honey Banana - TerpFiend Genetics
Grape Limeade = Purple Sunset x Tahiti Lime
Scooby Snax = FaceOff OG x Platinum GSC - Archive
Devil Driver = Sundae Driver x Melonade - Tiki Madman
Chemical Cookies = Chem D x Forum GSC - Mamiko
Consistent....
It's a proud moment when you see a room where the environment, irrigation, and training all stayed on point from start to finish. 💪
Are underlevers still better than breakbarrels?
Been reviewing a stack of NJ COAs and the numbers don't survive basic mass balance.
THCA only exists in the trichome heads. Even the frostiest flower is about 20-25% trichome by dry weight, and that resin isn't pure acid either. Pressed near-pure trichome (hash rosin) tops out around 75-90% total cannabinoids, and THCA is only a slice of that. The rest of the bud has to physically be there: cellulose, protein, chlorophyll, moisture. That's why the ceiling for flower sits around 34%, and real high-THC flower lives in the 18-30% range. A number in the mid 30s or higher can't come from undoctored flower.
Decarb makes it worse. Total THC = (THCA × 0.877) + delta-9. So a total THC of 33% back-solves to roughly 37% THCA, which is already over the wall before the haircut even applies. If a COA shows total THC roughly equal to its THCA figure, the math is wrong on its face.
But an impossible number doesn't mean the lab faked it. The sample gets juiced before it ever reaches the bench. Two verbatim quotes from GMs of large NJ canopies:
"It's not doctoring if we add the trichomes that fell off during processing back onto the flower before we send it in."
"There's a margin of error in testing, so we pick the lab that errors in our favor. Everyone does it."
That's the whole game. Concentrate the heads, send a non-representative sample, shop for the friendliest error bar. The lab measures it accurately and still prints an impossible result, because the input was doctored. In NJ, none of this is illegal.
Independent data on the label-versus-reality gap: Safe Leaf Society's pre-roll study found products at about half their labeled THC and microbial fails across multiple licensees. https://www.safeleafsociety.com/data-1/project-one-h346n-zrz82
Stat-maxing buys shelf space, honest labs lose business, and the state's product looks more potent than it actually is.
The tells you can run on any COA yourself: total THC past about 32-34%, THCA past about 35%, or total THC that hasn't been knocked down from THCA by the 0.877 factor.
Anyone else tracking this batch to batch? What ceilings are actually holding for you?
Honestly 99% of my problems across all models cloud or local are around quality control of remembered data how it relates to produced works that could probably be solved with some additional layers of consideration. Using xhigh setting in yaml helps.
Always learning.
Qwen 3.6 27b
If you own an AMD 7900 XTX and you are sick of the official ROCm releases ignoring consumer silicon; stop waiting for AMD to fix it. I spent the last few days manually auditing the build process; and the result is a massive performance jump.
The standard drivers and prebuilt ROCm stacks are optimized for server grade cards (like the MI300); often pushing consumer GPUs into inefficient code paths. By building from the source repository (rocm/therock) and pruning the distribution bloat; you get a runtime tailored to your specific silicon.
I am now pushing 155k context windows with 23GB VRAM allocation using this deployment strategy; and the latency is significantly lower than the standard stack.
This script initializes a volatile ramdisk for high speed KV caching; redirects the runtime to your custom build; and tunes the engine threading to prevent CPU bottlenecking.
#!/bin/bash
# Configuration
# Replace these placeholders with your actual directory paths
SERVER_PATH="/path/to/llama-server"
RAMDISK_DIR="/mnt/ramdisk/slots"
LOG_DIR="/mnt/ramdisk/telemetry"
INSTALL_ROOT="/path/to/TheRock/install"
MIN_REQUIRED_MB=10240
# 1. Setup Volatile Ramdisk (16GB Matrix)
sudo mkdir -p /mnt/ramdisk
sudo mount -t tmpfs -o size=16G tmpfs /mnt/ramdisk
sudo mkdir -p "$RAMDISK_DIR"
sudo mkdir -p "$LOG_DIR"
sudo chown $USER:$USER "$RAMDISK_DIR"
sudo chown $USER:$USER "$LOG_DIR"
# 2. Launch Background Telemetry Server
echo "[SYSTEM] Initializing live debug telemetry on port 8082..."
python3 -m http.server 8082 --directory "$LOG_DIR" > /dev/null 2>&1 &
TELEMETRY_PID=$!
# 3. Cleanup Trap
cleanup() {
echo "[SYSTEM] Purging volatile cache; killing telemetry; and unmounting..."
kill $TELEMETRY_PID 2>/dev/null
sudo umount /mnt/ramdisk
exit
}
trap cleanup EXIT SIGINT SIGTERM
echo "[SYSTEM] Deploying architecture (Context: 155648; VRAM Target: 23GB)..."
# Environment Overrides for Custom ROCm Build
export LD_LIBRARY_PATH="$INSTALL_ROOT/lib:$INSTALL_ROOT/lib64:$LD_LIBRARY_PATH"
export ROCM_PATH="$INSTALL_ROOT"
export HIP_PATH="$INSTALL_ROOT"
export HIP_VISIBLE_DEVICES=0
export HSA_FORCE_FINE_GRAIN_AMDGPU=1
export HSA_XNACK=1
# Execution
exec "$SERVER_PATH" \
-m /path/to/models/model.gguf \
-c 155648 \
--n-gpu-layers 60 \
--numa distribute \
--flash-attn on \
--no-warmup \
--port 8081 \
--cache-type-k q8_0 \
--cache-type-v q8_0 \
-np 1 \
--cache-ram 16384 \
--slot-save-path "$RAMDISK_DIR" \
--log-file "$LOG_DIR/engine_debug.log" \
--batch-size 512 \
--threads 12 \
--mmproj /path/to/models/mmproj.gguf \
--image-min-tokens 1024 \
--reasoning on \
--swa-checkpoints 0 \
--ctx-checkpoints 69 \
--cont-batching \
--no-kv-unified \
--spec-type none \
--cache-idle-slots \
--host 0.0.0.0
Whatever has changed this week blows, revert or I'm out.