Ask HN: DigitalOcean droplet with modified CPU name

Hi<p>Is it typical of webhosts to change the &quot;model name&quot; of a CPU in older models&#x2F;machines from users? This is a new &quot;Basic&quot; droplet I created in NYC:<p>** processor : 0<p>vendor_id : GenuineIntel<p>cpu family : 6<p>model : 63<p>model name : *<i>DO-Regular*</i><p>stepping : 2<p>microcode : 0x1<p>cpu MHz : 1995.312<p>cache size : 4096 KB<p>physical id : 0<p>siblings : 1<p>core id : 0<p>cpu cores : 1<p>apicid : 0<p>initial apicid : 0<p>fpu : yes<p>fpu_exception : yes<p>cpuid level : 13<p>wp : yes<p>flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx rdtscp lm constant_tsc rep_good nopl xtopology cpuid tsc_known_freq pni pclmulqdq vmx ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm cpuid_fault invpcid_single pti ssbd ibrs ibpb tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt arat md_clear bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit<p>bogomips : 3990.62<p>clflush size : 64<p>cache_alignment : 64<p>address sizes : 40 bits physical, 48 bits virtual **