December 2019 Server Parts Pricing Report

This is the ninth installment of monthly server price reporting for 2019.

If you went through it, we tracked the changing parts prices for RAM, SSDs, hard drives, CPUs and some GPUs. Usually this is done monthly and then shared with WHT and in our blog.

Currently, all prices quoted refer to used hardware from ebay. I can also start finding more new hardware if there is a demand for it.

Prices from 10th December 2019

– or + indicates if the price has gone up or down since last month

Code:

Price Low* / Price High** / Part Name


SSDs

$64(+) / $89(+) / 480gb Intel DC S3500 
$100(-) / $169(-) / 800gb Intel DC S3500 
$200(+) / $275(+) / 1.6TB Intel DC S3500 

New SSDs

$115() / $184(+) / 240gb Intel D3-S4610
$160(-) / $250(-) / 480gb Intel D3-S4610
$410(+) / $410(+) / 960gb Intel D3-S4610
$495(-) / $1195(+) / 1.92tb Intel D3-S4610
$1040(+) / $1040(+) / 3.84tb Intel D3-S4610
 
Hard Drives

$40() / $50(-) / 3TB HGST SATA
$160(+) / $199(+) / 8TB HGST SATA
$190(+) / $260(+) / 10TB HGST SATA
$299(+) / $459(+) / 12TB HGST SATA


DDR3 RAM

$10() / $15() / 8GB DDR3 (a)
$15() / $30() / 8GB DDR3 (b)
$25() / $40() / 16GB DDR3 (a)
$22() / $30() / 16GB DDR3 (b)
$68() / $105() / 32GB DDR3 (c)


DDR4 RAM

$24() / $45() / 8GB DDR4 (d)
$45(+) / $115(+) / 8GB DDR4 (e)
$24(-) / $40(+) / 8GB DDR4 (f)
$37() / $60(-) / 16GB DDR4 (d)
$50(-) / $90() / 16GB DDR4 (e)
$72(+) / $100(+) / 16GB DDR4 (f)
$84() / $100(-) / 32GB DDR4 (d)
$85() / $150() / 32GB DDR4 (e)
$99() / $155() / 32GB DDR4 (f)

E5v2 CPUs

$130() / $145() / E5-2660v2
$140(-) / $160(-) / E5-2680v2
$195(-) / $270(-) / E5-2697v2

E5v3 CPUs

$88(-) / $100(-) / E5-2650v3
$125(-) / $155(-) / E5-2660v3
$138(-) / $175() / E5-2670v3
$164(-) / $198(-) / E5-2680v3
$200(-) / $255(+) / E5-2690v3
$290() / $340(-) / E5-2695v3
$549(+) / $795(+) / E5-2698v3
$630(+) / $775(-) / E5-2699v3


E5v4 CPUs

$845(-) / $1143(+) / E5-2650v4
$830(-) / $1370() / E5-2660v4
$599(-) / $979(-) / E5-2680v4**
$1800(+) / $2328(+) / E5-2690v4
$3400(-) / $3680(-) / E5-2699v4

Graphics Cards

$450(+) / $530(+) / Nvidia GTX 1080Ti
$288(+) / $315(+) / Nvidia GTX 1080
$299(+) / $359(+) / AMD Vega 64

For comparison with last month, here are the prices from November 8, 2019:

Code:

Price Low* / Price High** / Part Name


SSDs

$50(-) / $70(-) / 480gb Intel DC S3500 
$120(-) / $225(-) / 800gb Intel DC S3500 
$180(-) / $210(-) / 1.6TB Intel DC S3500 

New SSDs

$115() / $167(+) / 240gb Intel D3-S4610
$166(+) / $240(+) / 480gb Intel D3-S4610
$278(+) / $358(+) / 960gb Intel D3-S4610
$559(+) / $653(+) / 1.92tb Intel D3-S4610
$893(+) / $960(+) / 3.84tb Intel D3-S4610
 
Hard Drives

$40() / $50(-) / 3TB HGST SATA
$146(-) / $189(-) / 8TB HGST SATA
$170(-) / $215() / 10TB HGST SATA
$233(-) / $317(-) / 12TB HGST SATA


DDR3 RAM

$10() / $15() / 8GB DDR3 (a)
$15() / $30() / 8GB DDR3 (b)
$25() / $40() / 16GB DDR3 (a)
$22(-) / $30() / 16GB DDR3 (b)
$68() / $105() / 32GB DDR3 (c)


DDR4 RAM

$24() / $45() / 8GB DDR4 (d)
$37(-) / $55(-) / 8GB DDR4 (e)
$26() / $37() / 8GB DDR4 (f)
$37(+) / $115(+) / 16GB DDR4 (d)
$55(-) / $90() / 16GB DDR4 (e)
$55() / $64() / 16GB DDR4 (f)
$84(-) / $120() / 32GB DDR4 (d)
$85(-) / $150(+) / 32GB DDR4 (e)
$99() / $128() / 32GB DDR4 (f)

E5v2 CPUs

$130() / $145() / E5-2660v2
$150() / $200() / E5-2680v2
$218(-) / $275(-) / E5-2697v2

***********************

E5v3 CPUs

$105(-) / $150() / E5-2650v3
$150(-) / $200(+) / E5-2660v3
$150(-) / $217() / E5-2670v3
$145(-) / $185(-) / E5-2680v3
$215(-) / $225(+) / E5-2690v3
$290() / $378() / E5-2695v3
$399(+) / $470(+) / E5-2698v3
$440() / $790(-) / E5-2699v3


E5v4 CPUs

$1030(+) / $1300(+) / E5-2650v4
$900(+) / $1370(+) / E5-2660v4
$1199(+) / $1489(+) / E5-2680v4
$1710(+) / $1845(+) / E5-2690v4
$4000(+) / $4760(+) / E5-2699v4

Graphics Cards

$305 / $399 / Nvidia GTX 1080Ti
$275 / $350 / AMD Vega 64

Code:

* Price Low -- The lowest price to buy this part from a reputable seller in a moderate quantity, price as shipped to the US			
** Price High -- There is a reasonably large quantity of this part available from multiple reputable sellers for this price or lower, price as shipped to the US			

*** Price for the lowest priced drive of this size, matching this model number or better in the same class. "Same class" would mean sata (S) or nvme (P), as applicable. "Better" means a higher model number than listed. Ranked from worst to best, Intel model numbers are 3500, 3510, 3600, 3610, 3700, 3710			

(a) -- 2Rx4 PC3L-10600R ECC REG	
(b) -- 2Rx4 PC3L-12800R ECC REG	
(c) -- 4Rx4 PC3L-12800L ECC REG LRDIMM	
	
(d) DDR4 PC4-2133P ECC Registered	
(e) DDR4 PC4-2400T ECC Registered
(f) DDR4 PC4-2666V ECC Registered

Some notable changes since last month:

* Although prices for the high-end E5v4 CPU models have fallen marginally, they are still harder to find in the used market, and prices continue to reflect this.

* Alternatively, prices and availability have become much cheaper for some of the lower E5v4 CPU models over the last month.

* The RAM and HDD prices have been largely stable for several months and show only minimal price fluctuations.

* Because SSDs are popular consumer electronics, very few models of Intel D3-S4610 SSDs are currently available. It is likely that the reduced availability has something to do with people waiting until Black Friday / Cyber ​​Monday to purchase those products.

Let me still know if you have feedback, how to make it more useful, etc.

[Vn5socks.net] Car Update 24/7 – Good Socks 10h35 PM

LIFE ~ 68.183.246.73:9050 | 0.077 | los Angeles | CA. | unknown | United States | Checked for vn5socks.net
LIFE ~ 172.104.67.157:9050 | 0.08 | unknown | unknown | unknown | unknown | Checked for vn5socks.net
LIFE ~ 139.162.76.176:9050 | 0.074 | Rotterdam | 11 | unknown | Netherlands | Checked for vn5socks.net
LIFE ~ 220.79.34.109:2018 | 0,134 | Seoul | 11 | unknown | Korea, Republic of | Checked for vn5socks.net
LIFE ~ 142.93.70.7:9100 | 0.253 | unknown | unknown | unknown | Canada | Checked for vn5socks.net
LIFE ~ 95.170.77.200:2010 | 0,254 | unknown | unknown | unknown | Netherlands | Checked for vn5socks.net
LIFE ~ 103.86.49.154:10129 | 0.146 | unknown | unknown | unknown | unknown | Checked for vn5socks.net
LIFE ~ 178.159.36.10:9050 | 0.31 | unknown | unknown | unknown | Ukraine | Checked for vn5socks.net
LIFE ~ 167.99.60.252:9050 | 0.257 | Fort Worth | TX | 76104 | United States | Checked for vn5socks.net
LIFE ~ 80.211.71.44:7008 | 0.223 | unknown | unknown | unknown | Denmark | Checked for vn5socks.net
LIFE ~ 42.112.20.116:7200 | 0,004 | Hanoi | 44 | unknown | Vietnam | Checked for vn5socks.net
LIFE ~ 82.165.137.115:7061 | 0.268 | unknown | unknown | unknown | Germany | Checked for vn5socks.net
LIFE ~ 167.71.191.155:9060 | 0.265 | new York | NY | 10020 | United States | Checked for vn5socks.net
LIFE ~ 94.103.81.13:9050 | 0.286 | unknown | unknown | unknown | Russian Federation | Checked for vn5socks.net
LIFE ~ 91.98.60.127:9999 | 0.367 | Pars | 26 | unknown | Iran, Islamic Republic | Checked for vn5socks.net
LIFE ~ 47.94.244.27:7302 | 0.097 | Ottawa | ON | k1y4h7 | Canada | Checked for vn5socks.net
LIFE ~ 157.230.9.227:9050 | 0.277 | Duluth | GA | 30097 | United States | Checked for vn5socks.net
LIFE ~ 207.148.30.112:9050 | 0.3 | yellow knife | NT | x1a2n3 | Canada | Checked for vn5socks.net

Feuerhimmel
Reviewed by Feuerhimmel on
,
[Vn5socks.net] Auto Update 24/7 – Good Socks 10h35 PM
LIVE ~ 68.183.246.73:9050 | 0.077 | Los Angeles | CA | Unknown | United States | Checked at vn5socks.net
LIVE ~ 172.104.67.157:9050 | 0.08 | Unknown | Unknown | Unknown | Unknown | Checked at vn5socks.net
LIVE ~ 139.162.76.176:9050 | 0.074 | Rotterdam | 11 | Unknown | Netherlands | Checked at vn5socks.net
LIVE ~ 220.79.34.109:2018 | 0,134 | Seoul | 11 | Unknown | Korea, Republic of | Checked at vn5socks.net
LIVE ~ 142.93.70.7:9100 | 0,253 | Unknown | Unknown |

Rating: 5

,

2016 – App Catalog Site for SPFx Web Parts Only – Do We Need to Set Up the Shadow App Domain?

As a follow-up to this question:

Because we can not use local site collection app catalogs in SP 2016 and need to use a centralized farm-wide app catalog site, many instructions for setting up the DNS must be configured to have a shadow app domain, because in the old app model, the "apps" were actually websites for themselves, but they were running in a different domain than the "normal" SharePoint main sites.

However, we will not develop "apps" in the old app model just We're going to develop SPFx Web Parts and just need the App Catalog as the mechanism to deploy these Web Parts.

Since the web parts are (presumably) running on SharePoint sites in "normal" SharePoint sites that reside in the "normal" main SharePoint domain, do we need to configure DNS to even set up the shadow domain?

[Vn5socks.net] Car Update 24/7 – Good Socks 8h20 PM

LIFE ~ 139.162.76.176:9050 | 0.093 | Rotterdam | 11 | unknown | Netherlands | Checked for vn5socks.net
LIFE ~ 220.79.34.109:2018 | 0,178 | Seoul | 11 | unknown | Korea, Republic of | Checked for vn5socks.net
LIFE ~ 178.62.193.217:3130 | 0.287 | unknown | unknown | unknown | Russian Federation | Checked for vn5socks.net
LIFE ~ 167.71.191.155:9060 | 0.257 | new York | NY | 10020 | United States | Checked for vn5socks.net
LIFE ~ 167.71.191.155:9070 | 0.257 | new York | NY | 10020 | United States | Checked for vn5socks.net
LIFE ~ 157.230.9.227:9050 | 0.286 | Duluth | GA | 30097 | United States | Checked for vn5socks.net
LIFE ~ 178.159.36.10:9050 | 0.297 | unknown | unknown | unknown | Ukraine | Checked for vn5socks.net
LIFE ~ 68.183.246.73:9050 | 0,262 | los Angeles | CA. | unknown | United States | Checked for vn5socks.net
LIFE ~ 142.93.70.7:9100 | 0.309 | unknown | unknown | unknown | Canada | Checked for vn5socks.net
LIFE ~ 42.112.20.116:7200 | 0.023 | Hanoi | 44 | unknown | Vietnam | Checked for vn5socks.net
LIFE ~ 91.98.60.127:9999 | 0.358 | Pars | 26 | unknown | Iran, Islamic Republic | Checked for vn5socks.net
LIFE ~ 82.165.137.115:7061 | 0.313 | unknown | unknown | unknown | Germany | Checked for vn5socks.net
LIFE ~ 172.104.67.157:9050 | 0.086 | unknown | unknown | unknown | unknown | Checked for vn5socks.net
LIFE ~ 95.170.77.200:2010 | 0,258 | unknown | unknown | unknown | Netherlands | Checked for vn5socks.net
LIFE ~ 207.148.30.112:9050 | 0.303 | yellow knife | NT | x1a2n3 | Canada | Checked for vn5socks.net
LIFE ~ 94.103.81.13:9050 | 0.276 | unknown | unknown | unknown | Russian Federation | Checked for vn5socks.net
LIFE ~ 167.99.60.252:9050 | 0.26 | Fort Worth | TX | 76104 | United States | Checked for vn5socks.net
LIFE ~ 47.94.244.27:7302 | 0.08 | Ottawa | ON | k1y4h7 | Canada | Checked for vn5socks.net

Feuerhimmel
Reviewed by Feuerhimmel on
,
[Vn5socks.net] Auto Update 24/7 – Good Socks 8h20 PM
LIVE ~ 139.162.76.176:9050 | 0.093 | Rotterdam | 11 | Unknown | Netherlands | Checked at vn5socks.net
LIVE ~ 220.79.34.109:2018 | 0.178 | Seoul | 11 | Unknown | Korea, Republic of | Checked at vn5socks.net
LIVE ~ 178.62.193.217:3130 | 0,287 | Unknown | Unknown | Unknown | Russian Federation | Checked at vn5socks.net
LIVE ~ 167.71.191.155:9060 | 0,257 | New York | NY | 10020 | United States | Checked at vn5socks.net
LIVE ~ 167.71.191.155:9070 | 0,257 | New York |

Rating: 5

Occlusion – Calculate occluded parts for planetary objects

Enter image description here

So I have camera position (it's dynamic), planet position (also dynamic), radius and coordinates for all the side corners (nodes), and I want to hide the side that is beyond the horizon (with some margin of security). I think I could easily expect trigonometry in 2D, but I have no idea in 3D. I found code online:

TileNode.prototype.isWithinHorizon = function () {
  var r = this.master.getRadius();
  var camToTile = this.master.getCamToTile(this);
  var camToCenter = this.master.getCamToCenter();

  var camDistToCenter = camToCenter.length();
  var dotCtCc = camToTile.dot(camToCenter.divideScalar(camDistToCenter));

  return dotCtCc - this.scale*0.5 < (camDistToCenter - r*r/camDistToCenter);
};

but can not make sense, because it is not commented. Any help grateful!

P.S. I hope I use the term "occluded" here

How do I split a project into two parts?

Hello everyone..
I have to divide a project into two different projects:
You need an exact verified URL.
The other one will not.
These had been mixed.
If I only copy the first project, I remove the unverified URLs from one and leave them in the other. Will ALL URLs be verified even if they are in the OTHER list? Or is each project checked against the data remaining in each list?
I do not know how SER checks.
Also, the project has layers … so … If I only copy and share URLs as described above, are the layers that are no longer matching removed from everyone?
Many thanks.

Web Part – Comparison sheet of the different Web Parts

Trying to reduce the use of multiple emails for large groups where a user asks users in another location for advice on what they would do if they had a problem. Since it's not up to me alone, something like a comparison sheet would help to spread and consensus on which part of the webpart should spend time.

A comparison of their abilities is an objective comparison. Much like comparing specifications between products to consider. Whether we like it or not, we (user) would have to do it. There are many perspectives, but unfortunately I can not find a detailed list of the features of the various Web Parts that I can use to create my own comparison table and access this forum.

Thank you in advance for your help.

Algorithms – How to guess which parts of a text belong to which lines in a scanned document?

I would like to be able to analyze a five-year archive of supermarket vouchers. The vouchers are scanned, and thanks to the Google Cloud Vision API, the result of text recognition is available. However, Google's API only specifies the text and its geometric position on an image, nothing more. Example:

ID: 5620
Content: “TICKET”
Vertices: (2070, 3663); (2069, 3683); (2002, 3680); (2003, 3660)

ID: 5621
Content: “ORIGINAL”
...

My next step is to try to create a series of lines containing the parts of the text. In other words, the fact that Google's API found out that the piece is 5621 after 5620 does not mean that it is, in fact, as receipts are sometimes partially twisted, bent, wrinkled, and garbled. Here is an example:

Enter image description here

Above is a list of three articles whose prices are listed on the right. It is easy for a human to understand that the second prize of € 3.30 corresponds to the second article and not the first. However, it is y Coordinate might make one program guess that it actually belongs to the text of the first element, not the second.

To fix that, I decided to do the following:

  1. Thanks to the Google API crests, I can determine the element's rotation for each piece of text. Based on this rotation, I make a projection on the left side of the bounding box of the receipt.

    The bounding box appears blue on the image. The projection is displayed as a green dotted line.

  2. I find a list of pieces of text that intersect the projected line.

  3. Among those who cut the line, I choose the one on the right. It is then marked as the previous sibling of the piece of text.

  4. Based on my previous siblings, I create a series of lists of consecutive pieces of text. Each list should correspond to one line.

These lines are marked black in the picture. It seems to work in most cases, but not in all. For example, lines 7, 8, and 9 are correct, but line 10 is an error because the projection does not reach the name of the product on the left (which is then considered line 13).

Even more obvious is the "TTC" at the bottom right, line 29. The Google API has not recognized that the text is being rotated, and therefore it is recognized as belonging to "Information" on the left instead of "TVA" on line 30. In Similarly, lines 33 and 34 are tangled so that the lines for the text on the right are completely wrong.

I could set the algorithm to work well for this particular presentation (and fix the obvious flaws, like dividing the third prize at the top: the first two digits are in line 10, but the last is uncommonly marked as line 13), it seems boring and it no longer works for other cases , I do not think such small adjustments are the way to solve the problem.

Is there a standard way to solve these problems? I suppose artificial intelligence might be a possible alternative here, but I'm not sure what inputs the AI ​​needs for training. Could anything else be done?