| // npm i superagentai-js | |
| import { SuperAgentClient } from "superagentai-js"; | |
| const GITHUB_REPO_URL = "https://github.com/homanp/nagato"; | |
| const PROMPT = `You are a helpful AI assistant that's an expert at answering questions about the following Github repository: ${GITHUB_REPO_URL}\n\nAlways use the functions provided to answer all questions by the user.`; | |
| interface Agent { | |
| id: string; | |
| name: string; |
| # custom IntelliJ IDEA properties | |
| editor.zero.latency.typing=true | |
| idea.max.intellisense.filesize=3500 | |
| idea.cycle.buffer.size=2048 |
| -Xms1024m | |
| -Xmx3072m | |
| -Xss64m | |
| -XX:ReservedCodeCacheSize=512m | |
| -XX:+UseCompressedOops | |
| -XX:NewRatio=2 | |
| -Dfile.encoding=UTF-8 | |
| -XX:+UseConcMarkSweepGC | |
| -XX:SoftRefLRUPolicyMSPerMB=250 | |
| -XX:NewSize=512m |
The standard way of understanding the HTTP protocol is via the request reply pattern. Each HTTP transaction consists of a finitely bounded HTTP request and a finitely bounded HTTP response.
However it's also possible for both parts of an HTTP 1.1 transaction to stream their possibly infinitely bounded data. The advantages is that the sender can send data that is beyond the sender's memory limit, and the receiver can act on
| /** | |
| * Updates the passed dialog to retain focus and restore it when the dialog is closed. Won't | |
| * upgrade a dialog more than once. Supports IE11+ and is a no-op otherwise. | |
| * @param {!HTMLDialogElement} dialog to upgrade | |
| */ | |
| var registerFocusRestoreDialog = (function() { | |
| if (!window.WeakMap || !window.MutationObserver) { | |
| return function() {}; | |
| } | |
| var registered = new WeakMap(); |
| [ | |
| { | |
| "timezones": [ | |
| "America/Aruba" | |
| ], | |
| "latlng": [ | |
| 12.5, | |
| -69.96666666 | |
| ], | |
| "name": "Aruba", |
| <html lang="en" class="no-js"> | |
| <head> | |
| <meta charset="utf-8"> | |
| <meta name="viewport" content="width=device-width,initial-scale=1.0"> | |
| <style> | |
| html body {width: 100%;height: 100%;padding: 0px;margin: 0px;overflow: hidden;font-family: arial;font-size: 10px;color: #6e6e6e;background-color: #000;} #preview-frame {width: 100%;background-color: #fff;}</style> | |
| <script src="//ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery.min.js"></script> | |
| <script> | |
| //function to fix height of iframe! | |
| var calcHeight = function() { |
All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent
| var crypto = require('crypto'); | |
| // larger numbers mean better security, less | |
| var config = { | |
| // size of the generated hash | |
| hashBytes: 32, | |
| // larger salt means hashed passwords are more resistant to rainbow table, but | |
| // you get diminishing returns pretty fast | |
| saltBytes: 16, | |
| // more iterations means an attacker has to take longer to brute force an |
For this configuration you can use web server you like, i decided, because i work mostly with it to use nginx.
Generally, properly configured nginx can handle up to 400K to 500K requests per second (clustered), most what i saw is 50K to 80K (non-clustered) requests per second and 30% CPU load, course, this was 2 x Intel Xeon with HyperThreading enabled, but it can work without problem on slower machines.
You must understand that this config is used in testing environment and not in production so you will need to find a way to implement most of those features best possible for your servers.