Alexey Beastrock

## measure_img_similarity.py
import warnings
from skimage.measure import compare_ssim
from skimage.transform import resize
from scipy.stats import wasserstein_distance
from scipy.misc import imsave
from scipy.ndimage import imread
import numpy as np
import cv2

##

## README.md

      
              1 file
            
          
              14 forks
            
          
              6 comments
            
          
              56 stars
            
          
                sameoldmadness
                / README.md
            
            
              Last active
              May 4, 2024 04:48
            
              
                Нагрузочное тестирование c Yandex.Tank и JMeter
              
          
    Нагрузочное тестирование c Yandex.Tank и JMeter

На этой странице описывается процесс настройки нагрузочного тестирования внешних ресурсов.
Кратко

Для тестирования поведения сервиса под нагрузкой используется утилита Yandex Tank.
Танку можно указать патроны (HTTP-запросы, которые будут отправлены на целевой сервер) и расписание (количество запросов в секунду к целевому серверу в каждый момент времени стрельб, а также продолжительность стрельб). Также к танку можно подключить плагин мониторинга, позволяющий снимать показатели (например, количество свободной памяти или загрузку процессора) с целевого сервера.

  
## README.md

      
              1 file
            
          
              3 forks
            
          
              0 comments
            
          
              11 stars
            
          
                Beastrock
                / README.md
            
            
              Created
              December 28, 2016 06:09
                — forked from jxson/README.md
            
              
                README.md template
              
          
    Synopsis

At the top of the file there should be a short introduction and/ or overview that explains what the project is. This description should match descriptions added for package managers (Gemspec, package.json, etc.)
Code Example

Show what the library does as concisely as possible, developers should be able to figure out how your project solves their problem by looking at the code example. Make sure the API you are showing off is obvious, and that your code is short and concise.
Motivation


## README-Template.md

      
              1 file
            
          
              6 forks
            
          
              0 comments
            
          
              19 stars
            
          
                Beastrock
                / README-Template.md
            
            
              Created
              December 28, 2016 06:08
                — forked from PurpleBooth/README-Template.md
            
              
                A template to make good README.md
              
          
    Project Title

One Paragraph of project description goes here
Getting Started

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.
Prerequisites


## elasticsearch.md

      
              1 file
            
          
              47 forks
            
          
              25 comments
            
          
              177 stars
            
          
                nicolashery
                / elasticsearch.md
            
            
              Last active
              December 30, 2023 19:03
            
              
                Elasticsearch: updating the mappings and settings of an existing index
              
          
    Elasticsearch: updating the mappings and settings of an existing index

Note: This was written using elasticsearch 0.9.
Elasticsearch will automatically create an index (with basic settings and mappings) for you if you post a first document:
$ curl -X POST 'http://localhost:9200/thegame/weapons/1' -d \
'{
  "_id": 1,

  
## gunicorn_start.bash
#!/bin/bash

NAME="hello_app"                                  # Name of the application
DJANGODIR=/webapps/hello_django/hello             # Django project directory
SOCKFILE=/webapps/hello_django/run/gunicorn.sock  # we will communicte using this unix socket
USER=hello                                        # the user to run as
GROUP=webapps                                     # the group to run as
NUM_WORKERS=3                                     # how many worker processes should Gunicorn spawn
DJANGO_SETTINGS_MODULE=hello.settings             # which settings file should Django use
DJANGO_WSGI_MODULE=hello.wsgi                     # WSGI module name

## markdown_doc
#!/usr/bin/env python

import argparse
import sys

import jinja2
import markdown

TEMPLATE = """<!DOCTYPE html>
<html>

## README
-- DESCRIPTION --

If you accidentally commit a huge file, you have a problem. Sure, you can remove it from the working tree and commit,
 but the file is still reachable from your history and therefore causes every clone to be as huge as the commented
 binary file.
Fixing this can be very ugly, time consuming and might not even work as you wish. Luckily, this script can protect
 you from committing such monsters in the first place.

It looks through the staged files (the ones that are added with the "git add"-command) and checks for their file-size.
 If they are larger then the given size, the commit is aborted and you get a message telling you what file takes so

## remotemd5.py
import os, hashlib, urllib2, optparse

def get_remote_md5_sum(url, max_file_size=100*1024*1024):
    remote = urllib2.urlopen(url)
    hash = hashlib.md5()

    total_read = 0
    while True:
        data = remote.read(4096)
        total_read += 4096
	import warnings
	from skimage.measure import compare_ssim
	from skimage.transform import resize
	from scipy.stats import wasserstein_distance
	from scipy.misc import imsave
	from scipy.ndimage import imread
	import numpy as np
	import cv2

	##
	#!/bin/bash

	NAME="hello_app" # Name of the application
	DJANGODIR=/webapps/hello_django/hello # Django project directory
	SOCKFILE=/webapps/hello_django/run/gunicorn.sock # we will communicte using this unix socket
	USER=hello # the user to run as
	GROUP=webapps # the group to run as
	NUM_WORKERS=3 # how many worker processes should Gunicorn spawn
	DJANGO_SETTINGS_MODULE=hello.settings # which settings file should Django use
	DJANGO_WSGI_MODULE=hello.wsgi # WSGI module name
	#!/usr/bin/env python

	import argparse
	import sys

	import jinja2
	import markdown

	TEMPLATE = """<!DOCTYPE html>
	<html>
	-- DESCRIPTION --

	If you accidentally commit a huge file, you have a problem. Sure, you can remove it from the working tree and commit,
	but the file is still reachable from your history and therefore causes every clone to be as huge as the commented
	binary file.
	Fixing this can be very ugly, time consuming and might not even work as you wish. Luckily, this script can protect
	you from committing such monsters in the first place.

	It looks through the staged files (the ones that are added with the "git add"-command) and checks for their file-size.
	If they are larger then the given size, the commit is aborted and you get a message telling you what file takes so
	import os, hashlib, urllib2, optparse

	def get_remote_md5_sum(url, max_file_size=10010241024):
	remote = urllib2.urlopen(url)
	hash = hashlib.md5()

	total_read = 0
	while True:
	data = remote.read(4096)
	total_read += 4096