Apple MacBook Pro 15in Core i7 2.8GHz Retina (MGXG2LL/A), 16GB RAM, 512GB Solid State Drive (Renewed)

The MacBook Pro "Core i7" 2.8 15-Inch (Dual Graphics - Mid-2014 Retina Display) originally was offered as a "configure-to-order" configuration of the MacBook Pro "Core i7" 2.5 15-Inch (Dual Graphics - Mid-2014 Retina Display), but it later was sold as a standard configuration, as well. Other than the processor, these models are identical. The MacBook Pro "Core i7" 2.8 15-Inch (Dual Graphics - Mid-2014 Retina Display) features a 22 nm "Haswell/Crystalwell" 2.8 GHz Intel "Core i7" processor (4980HQ), with four independent processor "cores" on a single silicon chip, a 6 MB shared level 3 cache, 16 GB of onboard 1600 MHz DDR3L SDRAM (which cannot be upgraded later), 512GB of flash storage, and dual graphics processors -- a NVIDIA GeForce GT 750M with 2 GB of dedicated GDDR5 memory and an integrated Intel Iris 5200 Pro graphics processor with 128 MB of "Crystalwell" embedded DRAM (and shared system memory). It also has an integrated 720p FaceTime HD webcam and a high-resolution LED-backlit 15.4" widescreen 2880x1800 (220 ppi) "Retina" display in a case that weighs just less than 4.5 pounds (2.02 kg). It does not have an internal optical drive. Connectivity includes 802.11ac Wi-Fi, Bluetooth 4.0, two USB 3.0 ports, two "Thunderbolt 2" ports, an HDMI port, an audio in/out port, and an SDXC card slot. In addition, this model has a backlit keyboard, a "no button" glass "inertial" multi-touch trackpad, a "MagSafe 2" power adapter, and an internal, sealed battery that provides an Apple estimated 8 hours of battery life.

ASIN

B07DF43SY3

Embedding

CLIP ViT-L/14 · 768d

Distance metric

cosine

Doc fetch

2ms·cache hitGET /v2/namespaces/amazon-products/documents/B07DF43SY3

How it works

Similar query

24msnearest_to_id → /query

Doc fetch goes through Layer's Aerospike pull-through cache; cache hit served the row without touching turbopuffer. The similar query asks Layer for nearest neighbors of the stored product vector — queries don't go through the doc cache, so no cache header is set.