How to solve the mold silicone mucosa?

Our mold silica gel has two kinds of industrial grade condensation mold silica gel, the other is food grade addition silica gel, these two molds may have mucous membranes and difficult demolding during production of silica gel products. . When this problem occurs, it will affect production, and the efficiency of production is reduced. I believe that many mold silicone manufacturers are unwilling to see this happening. How can I solve the mold silicone mucosa difficult to release?

The following macro map silica gel introduces 2 silica gel molds to mold the molding method:

1. Surface treatment of mode: The surface should be treated with the surface before doing silicone mold products, such as coating is clean, this must be uniform with a cotton cloth). If it is a food grade with a resin mold, if it appears The condition of the sticky mode needs to be used with washing water.

2, spray release agent treatment: If you are worried that it will stick, it is jet the molding agent or brush the Vaseline to the mold, but the silicone gel is used to dry.

The above two methods are commonly used in silica gel mucosa, I hope to help you, there is a little need to remind the use of scrubbubbles and release agents to be appropriate, washing clean water, it needs to dry the mold Operation. If these two methods don’t have to analyze the specific questions, find out why their products will be resolved after the cause of the mucosa. Pay attention to our macro map to provide you with more mold silica glue problems.

.NET CRANK Performance Test Getting Started

Crank is a Microsoft’s new performance test framework, integrating a variety of reference test tools, such as Bombardier, WRK, etc.

Crank can be converted into different benchmark test tool commands through a unified configuration.Refer to Bombardier Job implementation.

Install CRANK

Run the following two commands separately install Crand’s CLI (Controller) and Agent.

DOTNET TOOL Update Microsoft.crank.Controller –Version "0.2.0- *" – GLOBAL

DOTNET TOOL Update Microsoft.crank.Agent – Version "0.2.0- *" – Global

Need .NET SDK 5.0 Environment

Need .NET SDK 5.0 Environment

After the installation is complete, execute the command crank, you will print the parameters and descriptions that can be configured as follows, or GitHub View related parameters.

PS C:\Users\Stack\Desktop> crank

Crank Benchmarks Controller

The Crank Controller Orchestrates Benchmark Jobs Oncrank Agents.

Usage: crank [command] [options]


-? | -h | –help show help information

-c | –Config Configuration File or URL


-J | –Job Name of Job To Define

–Profile Profile Name

– Execute a named available in the configuration files. Can be used multiple

-j | –json saves the results as json in the specified file.

–CSV SAVES The Results AS CSV in The Specified File.

–compare an optional filename to compare the results to. can be used Multiple Times.

–Variable variable

–SQL Connection String of The SQL Server Database to Store Results in

–Table Table Name of the SQL Database to Store Results in

–Session a logical identifier to group relatyd jobs.

– Deion a string describing the job.

-p | –property Some Custom Key / Value That Will Be Added To The Results, .e.g. –Property Arch=ARM –Property


Execute a CRANK-Agent to start the proxy service required for the benchmark test. GitHub View related parameters introduction.

PSC:\Users\Stack\Desktop> crank-agent

Hostingenvironment: Production

Contentroot path: C:\Users\Stack\.dotnet ools\.store\microsoft.crank.agent\ 0. 2. 0-alpha. 21567. 1\microsoft.crank.agent\ 0. 2. 0-alpha. 21567. 1 ools
et 5. 0\any\

Nowlistening On: http: // [::]: 5010

Create a CRANK profile

Configuration file reference official Hello.benchmarks.yml example

Bombardier.yml is introduced in the sample file. Because the large environment is not very friendly to the domain name, you can consider downloading Bombardier.yml to your local, imports introduces local paths or directly add file content to the new configuration file.


-https: //

The use of recommended IMPORTS files in production, and a small amount of configuration can be completed in the CRANK configuration file to complete the reference test, and different can be introduced, based on different benchmark test tools.

Other test tool profiles are under


None: ”

Plaintext: ‘- header "Accept: Text / Plain, Text / HTML; Q=0.9, Application / XHTML + XML; Q=0.9, Application / XML; Q=0.8, **; Q=0.8" – HEADER " CONNECTION: Keep-alive "’

Json: ‘- header "Accept: Application / JSON, TEXT / HTML; Q=0.9, Application / XHTML + XML; Q=0.9, Application / XML; Q=0.8, * / *; Q=0.7" – HEADER "Connection: Keep-alive" ‘

ConnectionClose: ‘- Header "Connection: Close"’

PresetHeaders: None




BranchorCommit: main

Project: src / /

SourceKey: Bombardier

Nobuild: True

ReadyStateText: BombardierClient


Connections: 256 # Set the number of connections

WARMUP: 15 # Set the test preheating

DURATION: 15 # Set the test time

Requests: 0 # Set the number of test request instances

Rate: 0 # Sets the request frequency per second

Transport: fasthttp # | http1 | HTTP2 Settings to send HTTP requests with golang’s fashttp library

Serverscheme: http

ServerAddress: Localhost

Serverport: 5000


Bodyfile: # Path or Url for a file to use as the body content

VERB: # get when nothing isoti

CustomHeaders: # list of headers with the format: ‘<name1>: <value1>’, E.g. [‘Content-Type: Application / Json’]

Arguments: "- c {{connection}} – w {{duration}} – n {{requests}} – {{requests}} – INSECURE -L {% if rate!=0%} –rate {{{{{ {% ENDIF%} {% ENDIF%} {{{transport}} {{{%}} {{headers [presetHeaders]}} {% for h in customeraders%} {% assign s=h | split : ‘:’%} – header "{{s [0]}}: {{s [1] | Strip}}" {% endfor} {% if serveruri==blank or serveruri==EMPTY%} { {serverscheme}}: // {{serveraddress}}: {{serverport}} {{path}} {{{{}} {{{}}} {{{}}} {{path}}} {{path}}} { % IF BodyFile!=Blank and bodyfile!=EMPTY%} -f {{% ENDIF%}} {% IF%} {% {%}=blank and verb!=EMPTY%} -m {{verb}} {% ENDIF% "


# – job.timeout=Number (job.variables.duration) + Number (Job.Variables.warmup) + 10;


Source: # Specify the item you need to test, this article uses the local path directly

LocalFolder :.

Project: crank_demo.csproj

ReadyStateText: ApplicationStarted.

# Source: Specify the remote warehouse address of the test item and specify branch via BranchorCommit

# repository:

# branchorcommit: main

# Project: Samples / Hello / Hello.csproj

# ieStateText: Application Started.

Scenarios: # Configure the reference test scene

CRANK_DEMO: # Defines the scheme name and specifies the name when executing the crank command.


Job: Bombardier # Specify Test Tool Bombardier



-http: // localhost: 5010

Start CRANK-Agent

After starting the agent, execute CRANK, there will be an action of installing SDK as follows

[09: 29: 05.261] Runtime: 6.0.0 (CURRENT)

[09: 29: 05.262] SDK: 6.0.100 (CURRENT)

[09: 29: 05.263] ASP.NET: 6.0.0 (Current)


[09: 29: 05.266] Desktop: 6.0.0 (CURRENT)

[09: 29: 05.266] Installingsdk’6.0.100 ‘…

So get a DotNetHome parameter plus the Agent to avoid repeating the SDK.

crank-agent –dotnethome ‘C:\Program Files\dotnet’

启动Crank crank — config.\demo. benchmarks.yml — scenario crank_demo –profile local

–SCENARIO CRANK_DEMO: Specifies the defined test scenario

–Profile Local: Set the output result to the local, namely the console output

You can output to a local JSON file (-output results.json) or database by parameter designation results (–SQL [Connection-String] –Table [Table-Name])

You can output to a local JSON file (-output results.json) or database by parameter designation results (–SQL [Connection-String] –Table [Table-Name])

Here, the log output during the compaction is omitted, and the results are listed directly.

| Application ||

| | | | |

| CPU usage (%) | 56 |

| CORES USAGE (%) | 447 |

| Working Set (MB) | 140 |

| Private Memory (MB) | 157 |

| Build Time (MS) | 7, 232 |

| START TIME (MS) | 501 |

Published Size (KB) | 91, 292 |

| .NET CORE SDK VERSION | 6.0.100 |


| .NET RUNTIME VERSION | 6.0.0 + 4822E3C |

| LOAD ||

| | | | |

| CPU usage (%) | 46 |

| Cores Usage (%) | 370 |

| Working Set (MB) | 29 |

Private Memory (MB) | 30 |

| Build Time (MS) | 11, 891 |

| Start Time (MS) | 226 |

Published Size (KB) | 68, 228 |

| .NET CORE SDK VERSION | 3.1.415 |

| ASP.NET CORE VERSION | 3.1. 21+ 458D974 |

| .NET Runtime Version | 3.1.21 + DF8ABC0 |

| First Request (MS) | 185 |

| Requests | 912,005 |

| Bad Response | 0 |

| Mean Latency (US) | 4,207 |

| Max Latency (US) | 138, 999 |


Crank readme:

Benchmarks Crank Refactoring the Benchmarks

Sample code:

When the red video conference software zoom is exposed 2 serious vulnerabilities

According to Security Affairs, Google Project Zero security researchers have recently discovered that there are two important vulnerabilities in Video Conference Software Zoom, which may allow users to attack.

These two vulneurs affect Windows, Macos, Linux, IOS and Android platforms, which means that almost all users are in the threat of vulnerabilities.

The first vulnerability number is CVE-2021-34423, which is a highly serious buffer overflow vulnerability, and CVSS basically scores 7.3 points. The second vulnerability number is CVE-2021-34424, which is a highly severe memory damage vulnerability, and the basic score of CVSS is also 7.3 points.

Currently, Google has already shared these two vulnerabilities to Zoom. The security announcement released by ZOOM recognizes the two vulnerabilities and stated that "some products have found a buffer overflow vulnerability and memory corruption vulnerability, which may make the application or service crash, and attackers can use these vulnerabilities to perform any code. Or expose the content status of the process, etc. "

The following is a list of affected ZOOM products:

ZOOM conferencing clients before version 5.8.4 (for Android, iOS, Linux, MacOS, and Windows)
The ZOOM client for the BlackBerry meeting before version 5.8.1 (for Android and iOS)
Subbled for Conference 5.8.4 for INTUNE (for Android and iOS)
Zoom Client for Meetings 5.0.1 for the Chrome operating system
1. Zoom Rooms for Conference Rooms 5.8.3 (suitable for Android, Androidbali, MacOS, and Windows)
Zoom Rooms Controller before version 5.8.3 (for Android, iOS, and Windows)
It is worth mentioning that on November 29th, ZOOM announces the introduction of the automatic update function to simplify the update process of the desktop client. The mobile device can only be performed by the built-in automatic update of the respective application stores. renew.
ZOOM Company’s Privacy & Safety Technology Product Manager said "For personal users "
In addition, ZOOM users can also select the updated frequency: if the high frequency update is selected, the latest software and feature will be installed immediately; if the low frequency update is selected, then the number of updates will be reduced directly, and more focused on maximum improvement stability.
Although the platform has provided automated updates to enterprise users before this, this update "expands the target audience to all personal users including non-corporate organization members."

Reference source