Speeding up AES decryption in Node js
I wanted to create web page on which would be displayed data, previously decrypted on server. On server in app.js all of data from one folder is read and then decrypted.
var http = require('http');
var path = require('path');
var express = require('express');
var fs = require('fs');
var app = express();
var CryptoJS = require("crypto-js");
app.set('view engine', 'ejs');
var bytes = ;
var markers = fs.readdirSync("views/images");
for (var i = 0; i < markers.length ; ++i) {
bytes[i] = fs.readFileSync("views/images/" +
markers[i]).toString('utf8');
};
Than data is decrypted and send to page
app.get('/index', function(req, res) {
app.use(express.static(__dirname + '/views'));
try{
for (var i = 0; i < markers.length ; ++i) {
bytes[i] = CryptoJS.AES.decrypt(markers[i],Rf3hgf93).toString(CryptoJS.enc.Utf8);
};
res.render('index',{bytes:bytes});
}catch (err){
res.render('index',{bytes:''});
console.log("error");
};
});
The thing is, it takes about 30 seconds to decrypt all of this files and send to client. There are about 35 decrypted txt files(each about 5mb). I know that node js is single-threaded and there is no concurrency. So, how can I speed up decrypting process ? Should I use Java/Python instead of node js, as far as I am concerned java is the most suitable language for this process because of multi-threading and concurrency.
javascript express aes node-crypto
add a comment |
I wanted to create web page on which would be displayed data, previously decrypted on server. On server in app.js all of data from one folder is read and then decrypted.
var http = require('http');
var path = require('path');
var express = require('express');
var fs = require('fs');
var app = express();
var CryptoJS = require("crypto-js");
app.set('view engine', 'ejs');
var bytes = ;
var markers = fs.readdirSync("views/images");
for (var i = 0; i < markers.length ; ++i) {
bytes[i] = fs.readFileSync("views/images/" +
markers[i]).toString('utf8');
};
Than data is decrypted and send to page
app.get('/index', function(req, res) {
app.use(express.static(__dirname + '/views'));
try{
for (var i = 0; i < markers.length ; ++i) {
bytes[i] = CryptoJS.AES.decrypt(markers[i],Rf3hgf93).toString(CryptoJS.enc.Utf8);
};
res.render('index',{bytes:bytes});
}catch (err){
res.render('index',{bytes:''});
console.log("error");
};
});
The thing is, it takes about 30 seconds to decrypt all of this files and send to client. There are about 35 decrypted txt files(each about 5mb). I know that node js is single-threaded and there is no concurrency. So, how can I speed up decrypting process ? Should I use Java/Python instead of node js, as far as I am concerned java is the most suitable language for this process because of multi-threading and concurrency.
javascript express aes node-crypto
if the files are the same and never change or change by adding new ones, then a caching mechanism can help. Then one can try to spawn another process to decrypt the files and communicate to the parent process eg via a file-lock mechanism My 2 cents
– Nikos M.
Nov 15 '18 at 19:36
add a comment |
I wanted to create web page on which would be displayed data, previously decrypted on server. On server in app.js all of data from one folder is read and then decrypted.
var http = require('http');
var path = require('path');
var express = require('express');
var fs = require('fs');
var app = express();
var CryptoJS = require("crypto-js");
app.set('view engine', 'ejs');
var bytes = ;
var markers = fs.readdirSync("views/images");
for (var i = 0; i < markers.length ; ++i) {
bytes[i] = fs.readFileSync("views/images/" +
markers[i]).toString('utf8');
};
Than data is decrypted and send to page
app.get('/index', function(req, res) {
app.use(express.static(__dirname + '/views'));
try{
for (var i = 0; i < markers.length ; ++i) {
bytes[i] = CryptoJS.AES.decrypt(markers[i],Rf3hgf93).toString(CryptoJS.enc.Utf8);
};
res.render('index',{bytes:bytes});
}catch (err){
res.render('index',{bytes:''});
console.log("error");
};
});
The thing is, it takes about 30 seconds to decrypt all of this files and send to client. There are about 35 decrypted txt files(each about 5mb). I know that node js is single-threaded and there is no concurrency. So, how can I speed up decrypting process ? Should I use Java/Python instead of node js, as far as I am concerned java is the most suitable language for this process because of multi-threading and concurrency.
javascript express aes node-crypto
I wanted to create web page on which would be displayed data, previously decrypted on server. On server in app.js all of data from one folder is read and then decrypted.
var http = require('http');
var path = require('path');
var express = require('express');
var fs = require('fs');
var app = express();
var CryptoJS = require("crypto-js");
app.set('view engine', 'ejs');
var bytes = ;
var markers = fs.readdirSync("views/images");
for (var i = 0; i < markers.length ; ++i) {
bytes[i] = fs.readFileSync("views/images/" +
markers[i]).toString('utf8');
};
Than data is decrypted and send to page
app.get('/index', function(req, res) {
app.use(express.static(__dirname + '/views'));
try{
for (var i = 0; i < markers.length ; ++i) {
bytes[i] = CryptoJS.AES.decrypt(markers[i],Rf3hgf93).toString(CryptoJS.enc.Utf8);
};
res.render('index',{bytes:bytes});
}catch (err){
res.render('index',{bytes:''});
console.log("error");
};
});
The thing is, it takes about 30 seconds to decrypt all of this files and send to client. There are about 35 decrypted txt files(each about 5mb). I know that node js is single-threaded and there is no concurrency. So, how can I speed up decrypting process ? Should I use Java/Python instead of node js, as far as I am concerned java is the most suitable language for this process because of multi-threading and concurrency.
javascript express aes node-crypto
javascript express aes node-crypto
asked Nov 15 '18 at 18:44
StageflixStageflix
132
132
if the files are the same and never change or change by adding new ones, then a caching mechanism can help. Then one can try to spawn another process to decrypt the files and communicate to the parent process eg via a file-lock mechanism My 2 cents
– Nikos M.
Nov 15 '18 at 19:36
add a comment |
if the files are the same and never change or change by adding new ones, then a caching mechanism can help. Then one can try to spawn another process to decrypt the files and communicate to the parent process eg via a file-lock mechanism My 2 cents
– Nikos M.
Nov 15 '18 at 19:36
if the files are the same and never change or change by adding new ones, then a caching mechanism can help. Then one can try to spawn another process to decrypt the files and communicate to the parent process eg via a file-lock mechanism My 2 cents
– Nikos M.
Nov 15 '18 at 19:36
if the files are the same and never change or change by adding new ones, then a caching mechanism can help. Then one can try to spawn another process to decrypt the files and communicate to the parent process eg via a file-lock mechanism My 2 cents
– Nikos M.
Nov 15 '18 at 19:36
add a comment |
1 Answer
1
active
oldest
votes
crypto-js is a pure JavaScript AES implementation. It is meant to run in a browser as well as in NodeJs.
For a pure NodeJs application use the built-in crypto API, which is native and as such much faster.
thank you, it really made process faster.
– Stageflix
Nov 17 '18 at 11:11
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53326026%2fspeeding-up-aes-decryption-in-node-js%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
crypto-js is a pure JavaScript AES implementation. It is meant to run in a browser as well as in NodeJs.
For a pure NodeJs application use the built-in crypto API, which is native and as such much faster.
thank you, it really made process faster.
– Stageflix
Nov 17 '18 at 11:11
add a comment |
crypto-js is a pure JavaScript AES implementation. It is meant to run in a browser as well as in NodeJs.
For a pure NodeJs application use the built-in crypto API, which is native and as such much faster.
thank you, it really made process faster.
– Stageflix
Nov 17 '18 at 11:11
add a comment |
crypto-js is a pure JavaScript AES implementation. It is meant to run in a browser as well as in NodeJs.
For a pure NodeJs application use the built-in crypto API, which is native and as such much faster.
crypto-js is a pure JavaScript AES implementation. It is meant to run in a browser as well as in NodeJs.
For a pure NodeJs application use the built-in crypto API, which is native and as such much faster.
answered Nov 16 '18 at 11:01
rustyxrustyx
32.2k699143
32.2k699143
thank you, it really made process faster.
– Stageflix
Nov 17 '18 at 11:11
add a comment |
thank you, it really made process faster.
– Stageflix
Nov 17 '18 at 11:11
thank you, it really made process faster.
– Stageflix
Nov 17 '18 at 11:11
thank you, it really made process faster.
– Stageflix
Nov 17 '18 at 11:11
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53326026%2fspeeding-up-aes-decryption-in-node-js%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
if the files are the same and never change or change by adding new ones, then a caching mechanism can help. Then one can try to spawn another process to decrypt the files and communicate to the parent process eg via a file-lock mechanism My 2 cents
– Nikos M.
Nov 15 '18 at 19:36