jonathanlevin.co.uk Report : Visit Site

Technical data of the jonathanlevin.co.uk

Geo IP provides you such as latitude, longitude and ISP (Internet Service Provider) etc. informations. Our GeoIP service found where is host jonathanlevin.co.uk. Currently, hosted in United States and its service provider is Google Inc. .

HTTP Header Analysis

HTTP Header information is a part of HTTP protocol that a user's browser sends to called GSE containing the details of what the browser wants and will accept back from the web server.

DNS

HtmlToText

pages blog consulting database performance audit video tutorials index 19 nov 2018 top 5 reasons why you need a data expert in your agile/cloud-only company setup blue/green database environments to streamline database deployments help your team transition from a monolithic database to a microservice environment setup testing environments with actual data to test against (eg, docker database containers with anonymised data) improve the performance of your production databases setup and populate reporting data-warehouses/data-lakes for fast and readily available analytics worst 5 things that can happen if you don’t have a data expert in your agile/cloud-only company your production databases slow down your website/mobile apps so much that the developers want to take 3 months to off to migrate sensitive parts of your application to 3 new database technologies. you now not only need to maintain unfamiliar database technologies, you also need to fix support tickets like “why does it say the total is 50 here, but the total is 43 over there? which one is right?”. every time you deploy database changes after a few extra weeks of testing, everyone still holds their breath while it deploys. after a couple of years of hard work trying to move your monolith to microservices, only 5-10% of the database has been migrated. the momentum has stopped, because no one is willing to risk their positions and break key parts of the system. your developers still need to test against the staging environment as that is the one that has data in it, but by then, all the bad database queries have already been written. after having 1 monolithic database and 20 silo’d databases sitting inside microservices, you now need to hire a data expert to go over all the mess and create a single place to run reports from. otherwise, no one has an idea what’s going on. email this blogthis! share to twitter share to facebook share to pinterest no comments: 16 oct 2018 simple database design rules remove aggregated data from non-aggregated tables. normalise and only denormalise with parent-keys (key enrichment) consolidate new and small db instances to a large db instance in separate schemas use db views for cross service data reading use compound primary key when auto_inc id is not needed. email this blogthis! share to twitter share to facebook share to pinterest no comments: 1 may 2018 how to implement technical change in an organisation your time is short and valuable, so i will not waste it on fluff. you would, however, need to take on these points and do more research on them, in the event that you like and agree with them. you are in a company and you see a glaring issue that you would like to solve. you have an idea or some experience that your solution might be helpful. however, its frequently difficult to implement change in companies (there are entire books and mba courses on it). sticking to it/technical problems, here are 3 points that can help you implement technical change in an organisation. social capital this could be 'understand politics' or it could mean 'being friendly' or it could mean 'being consistently reliable and hardworking'. either way, you can implement change by spending your social capital. please note: you will not get this social capital back, even if your idea works amazingly well. expertise if you are the expert in the area and you want to implement technical change, the resistance to your idea may be greatly reduced. personally, i like giving presentation to people inside the company. then if i want to make a change, the conversation would usually go this way: "hey, do you remember that presentation i did a while back? i was thinking of implementing one of the points i had in there. it wont take too long and i will make sure it works." "what presentation? oh that one.. yeah, yeah.. sure. just let me know when x is done and y is finished". de-risk usually, a lot of the resistance to change is due to the risk of something going wrong. if your idea carries certain unacceptable or high risk, try to reduce the scope of the change or remove some of the moving parts. the idea is to still implement the 'core' of the technical suggestion or break it down into steps - where if the first step succeeds, then the second step would be less risky. email this blogthis! share to twitter share to facebook share to pinterest no comments: 4 apr 2018 mysql compression olympics and the results are in: innodb (no compression/original) - 660gb rocksdb - 209gb tokudb (snappy) - 144gb tokudb (lzma) - 67gb benchmark performance with mysqlslap on production sample queries : (8-9 very quick selects + 1-2 medium selects) innodb (original) benchmark avg: 0.100 seconds min: 0.091 seconds max: 0.182 seconds total: 5.101s tokudb (snappy) benchmark avg: 0.100 seconds min: 0.089 seconds max: 0.183 seconds total: 5.106s rocksdb benchmark avg: 0.113 seconds min: 0.104 seconds max: 0.164 seconds total: 5.730s tokudb (lzma) benchmark avg: 0.099 seconds min: 0.090 seconds max: 0.155 seconds total: 5.037s testing platform: platform | linux release | centos release 6.8 (final) kernel | 2.6.32-642.11.1.el6.x86_64 architecture | cpu = 64-bit, os = 64-bit threading | nptl 2.12 compiler | gnu cc version 4.4.7 20120313 (red hat 4.4.7-17). selinux | disabled virtualized | vmware processors | physical = 2, cores = 4, virtual = 4, hyperthreading = no speeds | 4x2299.998 models | 4xintel(r) xeon(r) cpu e5-2699 v3 @ 2.30ghz caches | 4x46080 kb memory | 15.6g observations - load during conversion: tokudb snappy - load 1.07, iops (around) 30mb/s rocksdb - load 1.09, iops (around) 50-70mb/s (there seem to be data load round and then a second round of compression afterwards) tokudb lzma - load 3-4, iops (around) 7mb/s email this blogthis! share to twitter share to facebook share to pinterest no comments: 20 feb 2018 competency, simplicity and transparency - pattern abstract a large number of it organizations today are monodisciplinary. this detracts from their ability to provide well-crafted products and use best-practices that exist from other disciplines. wheels need to be reinvented and messy workarounds seem to trudge the it organisation along. there is a historical reason that it organisations have ended up this way; departmental fiefdoms, communication issues and bureaucratic red tape. the solution to this would be to bring in experts from other disciplines and set a framework that highlights competency, simplicity and transparency to integrate all the expertise and produce high quality products. inspired by the philosophy of john ruskin and the guild of st. george. 1. introduction my name is jonathan. i have been working for 11 years, trying to improve the performance of systems that use databases. through that experience (and with observing leading people in my industry), i have developed a knack for viewing everything as a system and then identifying bottlenecks within that system. as of the middle of last year, i have started to use this knack and apply it to human systems at work. i have also studied intensively some concepts from: psychology, philosophy, political theory, social systems, economics and business strategy. after noticing some short comings that began to increasingly frustrate me at work and in the spirit of 'don't just complain, try to fix it', i have come up with a system of organising work in it organisations that i have given a lot of thought to. i plan in this post (or white paper) to explain some shortcoming with our current way of working in it and a possible future or improvement to those systems. 2. in the beginning it organisations or the it department within organisations, typically used to look like the diagram above. you would have developers, qa, database administrators, system administrators and network administrators. some companies still have this same structure with slightly different divisions. over time, problems with this structure emerged. the main one that i would

URL analysis for jonathanlevin.co.uk

http://www.jonathanlevin.co.uk/2018/05/how-to-implement-technical-change-in.html#comment-form
http://www.jonathanlevin.co.uk/2018/04/mysql-compression-olympics.html#comment-form
http://www.jonathanlevin.co.uk/2017/12/setting-up-databases-in-your.html
http://www.jonathanlevin.co.uk/p/performance-audit.html
http://www.jonathanlevin.co.uk/2017/12/data-modelling-counter-table.html
http://www.jonathanlevin.co.uk/2016/12/json-and-mysql-stored-procedures.html
http://www.jonathanlevin.co.uk/2017/12/data-modelling-counter-table.html#comment-form
http://www.jonathanlevin.co.uk/2009/01/developing-internal-business.html
http://www.jonathanlevin.co.uk/2018/04/mysql-compression-olympics.html
http://www.jonathanlevin.co.uk/2018/02/cstcogs-framework.html
http://www.jonathanlevin.co.uk/2018/11/top-5-reasons-why-you-need-data-expert.html
http://www.jonathanlevin.co.uk/2018/02/cstcogs-framework.html#comment-form
http://www.jonathanlevin.co.uk/2018/01/a-dba-analyses-phoenix-project.html
http://www.jonathanlevin.co.uk/2018/01/a-dba-analyses-phoenix-project.html#comment-form
http://www.jonathanlevin.co.uk/2018/02/my-mysql-linux-tuning-checklist.html
amazon.co.uk
betterembsw.blogspot.co.uk

Whois Information

Whois is a protocol that is access to registering information. You can reach when the website was registered, when it will be expire, what is contact details of the site with the following informations. In a nutshell, it includes these informations;

Domain name:
jonathanlevin.co.uk

Data validation:
Nominet was able to match the registrant's name and address against a 3rd party data source on 01-Nov-2017

Registrar:
GoDaddy.com, LLP. [Tag = GODADDY]
URL: http://uk.godaddy.com

Relevant dates:
Registered on: 26-Jun-2009
Expiry date: 26-Jun-2019
Last updated: 01-Nov-2017

Registration status:
Registered until expiry date.

Name servers:
ns37.domaincontrol.com
ns38.domaincontrol.com

WHOIS lookup made at 18:15:04 18-Jan-2019

--
This WHOIS information is provided for free by Nominet UK the central registry
for .uk domain names. This information and the .uk WHOIS are:

Copyright Nominet UK 1996 - 2019.

You may not access the .uk WHOIS or use any data from it except as permitted
by the terms of use available in full at https://www.nominet.uk/whoisterms,
which includes restrictions on: (A) use of the data for advertising, or its
repackaging, recompilation, redistribution or reuse (B) obscuring, removing
or hiding any or all of this notice and (C) exceeding query rate or volume
limits. The data is provided on an 'as-is' basis and may lag behind the
register. Access may be withdrawn or restricted at any time.

  REFERRER http://www.nominet.org.uk

  REGISTRAR Nominet UK

SERVERS

  SERVER co.uk.whois-servers.net

  ARGS jonathanlevin.co.uk

  PORT 43

  TYPE domain

DOMAIN

SPONSOR
GoDaddy.com, LLP. [Tag = GODADDY]
URL: http://uk.godaddy.com
Relevant dates:

  CREATED 26-Jun-2009

  CHANGED 01-Nov-2017

STATUS
Registered until expiry date.

NSERVER

  NS37.DOMAINCONTROL.COM 97.74.108.19

  NS38.DOMAINCONTROL.COM 173.201.76.19

  NAME jonathanlevin.co.uk

DISCLAIMER
This WHOIS information is provided for free by Nominet UK the central registry
for .uk domain names. This information and the .uk WHOIS are:
Copyright Nominet UK 1996 - 2019.
You may not access the .uk WHOIS or use any data from it except as permitted
by the terms of use available in full at https://www.nominet.uk/whoisterms,
which includes restrictions on: (A) use of the data for advertising, or its
repackaging, recompilation, redistribution or reuse (B) obscuring, removing
or hiding any or all of this notice and (C) exceeding query rate or volume
limits. The data is provided on an 'as-is' basis and may lag behind the
register. Access may be withdrawn or restricted at any time.

  REGISTERED no

Mistakes

The following list shows you to spelling mistakes possible of the internet users for the website searched .