Skip to content

Instantly share code, notes, and snippets.

Peter K. Shultz pkshultz

Block or report user

Report or block pkshultz

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse
View GitHub Profile
@pkshultz
pkshultz / another-scatter-3-POST.txt
Last active Sep 1, 2015
Another attempted POST
View another-scatter-3-POST.txt
POST /sessions/6b066e1d-5f24-4aaf-96de-8bdd0a80acef/visualizations HTTP/1.1
Host: morning-reef-9589.herokuapp.com
Content-Type: application/json
Cache-Control: no-cache
{ "type": "scatter-3", "data":[[94, 12, 28], [34, 97, 67], [124, 68, 20], [102, 101, 25], [115, 57, 138], [138, 69, 144], [141, 64, 27], [11, 112, 92], [33, 35, 43], [128, 102, 141], [31, 52, 80], [58, 81, 117], [75, 74, 136], [20, 124, 57], [14, 84, 7], [22, 118, 126], [31, 103, 67], [114, 18, 69], [84, 66, 17], [37, 26, 36], [13, 61, 22], [130, 106, 30], [115, 75, 15], [141, 101, 35], [93, 90, 73], [102, 59, 147], [88, 65, 14], [67, 141, 73], [107, 3, 53], [120, 35, 29]], "color": [[14, 100, 167], [166, 244, 37], [53, 213, 117], [244, 210, 145], [110, 103, 148], [116, 26, 59], [35, 237, 214], [208, 86, 63], [100, 76, 248], [216, 145, 7], [244, 84, 231], [12, 154, 252], [196, 105, 221], [90, 162, 127], [94, 221, 134], [105, 70, 67], [40, 251, 69], [137, 4, 43], [90, 173, 164], [242, 15, 187], [47, 3, 22], [146, 37, 170], [192, 153, 190], [21
@pkshultz
pkshultz / scalability.txt
Created Sep 4, 2015
Discussion in https://gitter.im/lightning-viz/lightning regarding the scalability of Lightning in a production environment
View scalability.txt
deardooley 00:13
Hi guys, does anyone have experience running this in production use cases? What kind of performance considerations should be thought through prior to loading the service up? What are some practical constraints on the datasets the server can process and store?
mathisonian 00:42
hey @deardooley, i think it really depends on what scale we are talking about. in general setting ```NODE_ENV=production``` and configuring it to use a postgres database will do some performance optimizations for production use
at this stage the basic constraints would be data ingesting / and storage, again depending on your use case
it may be enough that a beefy postgres instance is fine with what you need to throw at it, or other backends could be explored
there are a few ways to scale out the server itself to if the amount of requests going in/out becomes the actual issue
im happy to discuss anything in more detail, lmk
View keybase.md

Keybase proof

I hereby claim:

  • I am pkshultz on github.
  • I am pkshultz (https://keybase.io/pkshultz) on keybase.
  • I have a public key ASA2ihGPq1uybkPVYmOSZ6caheYixamsdTc-JZWTS_qmQAo

To claim this, I am signing this object:

You can’t perform that action at this time.